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
..
.gitignore	gitignore: Update for in-place build.	2015-07-27 13:18:35 +01:00
lvmlockctl.c	cov: ensuring buffer is zeroed	2021-09-21 21:03:47 +02:00
lvmlockd-client.h	gcc: remove warning about inlining failure	2024-04-10 00:03:09 +02:00
lvmlockd-core.c	lvmlockd: check for multiple lock managers running	2024-04-19 10:53:37 -05:00
lvmlockd-dlm.c	lvmlocks: rework dm_strncpy	2024-04-04 19:38:21 +02:00
lvmlockd-idm.c	cleanup: free already does NULL check	2021-09-15 15:24:56 +02:00
lvmlockd-internal.h	debug: check for syscalls	2023-09-03 22:03:33 +02:00
lvmlockd-sanlock.c	lvmlockd: use sanlock.h for defines	2024-04-11 10:50:06 -05:00
Makefile.in	makefiles: use SHOW	2024-04-08 14:52:23 +02:00