David Teigland f32fd1fcb9 lvmlockd: adopt options ... Lock adoption is not part of standard command behavior, but can be used for manual recovery or cleanup from unexpected failure cases. Like other lockopt values, they are hidden options for --lockopt. Different lock managers will behave differently. Adopting locks with lvmlockd -A1 is more accurate and automatic. --lockopt adoptls . for vgchange --lockstart . adopt existing ls, or fail if no existing lockspace is found --lockopt adoptgl | adoptvg | adoptlv . for commands using lvmlockd locks . adopt orphan gl/vg/lv lock, or fail the lock request if no orphan lock is found . will fail if orphan lock exists with a different lock mode . command may still continue with a failed shared lock request --lockopt adopt . for lockstart or any command using lvmlockd locks . adopt existing lockspace, or start lockspace if none exists . adopt orphan gl/vg/lv lock, or acquire new lock if no orphan found . will fail if orphan lock exists with a different lock mode . command may still continue with a failed shared lock request . with dlm this option only works for ls		2024-06-27 13:29:03 -05:00
..
cmirrord	const: cmirrord array	2024-05-04 01:01:57 +02:00
dmeventd	gcc: ensure reset of fd on error path	2024-06-19 14:28:02 +02:00
lvmdbusd	lvmdbusd: its fine if dir already exists	2024-04-29 00:13:43 +02:00
lvmlockd	lvmlockd: adopt options	2024-06-27 13:29:03 -05:00
lvmpolld	cleanup: static missed _	2024-05-13 12:58:37 +02:00
Makefile.in	build: Remove lvmetad leftovers	2018-07-24 15:02:32 +02:00