David Teigland d0e15b86b5 lvmlockd: improve error message about missing global lock ... If the VG holding the global lock is removed, we can indicate that as the reason for not being able to acquire the global lock in subsequent error messages, and can suggest enabling the global lock in another VG. (This helpful error message will go away if the global lock is enabled in another VG, or if lvmlockd is restarted.)		2016-07-25 14:49:01 -05:00
..
.exported_symbols	Pre-release cleanups.	2009-05-21 03:04:52 +00:00
cluster_locking.c	doc: change fsf address	2016-01-21 12:11:37 +01:00
external_locking.c	doc: change fsf address	2016-01-21 12:11:37 +01:00
file_locking.c	Revert "locking: trace errors from dir creation"	2016-06-23 21:31:49 +01:00
locking_types.h	doc: change fsf address	2016-01-21 12:11:37 +01:00
locking.c	doc: change fsf address	2016-01-21 12:11:37 +01:00
locking.h	lvmetad: two phase vg_update	2016-06-28 02:30:31 +01:00
lvmlockd.c	lvmlockd: improve error message about missing global lock	2016-07-25 14:49:01 -05:00
lvmlockd.h	vgcreate: improve error message for multiple lock managers	2015-10-08 10:41:13 -05:00
Makefile.in	doc: change fsf address	2016-01-21 12:11:37 +01:00
no_locking.c	doc: change fsf address	2016-01-21 12:11:37 +01:00