Oracle Linux: "vgchange --lockstart" Fails With "lvmlockd[xxx]: xxx get_sizes_lockspace /dev/mapper/<vg_name>-lvmlock error -223" (Doc ID 2924446.1)

Last updated on JANUARY 30, 2023

Applies to:

Linux OS - Version Oracle Linux 7.0 and later
Information in this document applies to any platform.
Linux x86-64

Symptoms

After an unexpected storage outage on a shared VG with type sanlock, "vgchange --lockstart <vg_name>" could no longer access the sanlock(8) lockspace even with lvmlockd(8) running.

Restarting lvmlockd(8) does not help. Here is an example of repeated failures on an example VG vg_storage1.

Changes

Suffered an unexpected storage outage earlier.

Cause

	To view full details, sign in with your My Oracle Support account.
	Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.