David Teigland 85b711caae lvmlockd: check for multiple lock managers running ... When no lock manager for the global lock had been set yet, and the first global lock request was received, and both dlm and sanlock were running, lvmlockd would assume it should use the dlm for the global lock, and would start the "lvm_global" dlm lockspace automatically. That's not always correct, so don't assume the dlm should be used, fail the lock request, and wait until a VG with a specific lock type is started to determine the lock manager to use.		2024-04-19 10:53:37 -05:00
..
cmirrord	cov: pass buffer size	2024-04-10 00:03:09 +02:00
dmeventd	dmeventd: use daemon_close_stray_fds	2024-04-15 13:38:44 +02:00
lvmdbusd	makefiles: use SHOW	2024-04-08 14:52:23 +02:00
lvmlockd	lvmlockd: check for multiple lock managers running	2024-04-19 10:53:37 -05:00
lvmpolld	makefiles: use SHOW	2024-04-08 14:52:23 +02:00
Makefile.in	build: Remove lvmetad leftovers	2018-07-24 15:02:32 +02:00