David Teigland b4be988732 vgchange/lvchange: enforce the shared VG lock from lvmlockd ... The vgchange/lvchange activation commands read the VG, and don't write it, so they acquire a shared VG lock from lvmlockd. When other commands fail to acquire a shared VG lock from lvmlockd, a warning is printed and they continue without it. (Without it, the VG metadata they display from lvmetad may not be up to date.) vgchange/lvchange -a shouldn't continue without the shared lock for a couple reasons: . Usually they will just continue on and fail to acquire the LV locks for activation, so continuing is pointless. . More importantly, without the sh VG lock, the VG metadata used by the command may be stale, and the LV locks shown in the VG metadata may no longer be current. In the case of sanlock, this would result in odd, unpredictable errors when lvmlockd doesn't find the expected lock on disk. In the case of dlm, the invalid LV lock could be granted for the non-existing LV. The solution is to not continue after the shared lock fails, in the same way that a command fails if an exclusive lock fails.		2015-07-17 15:35:34 -05:00
..
toolcontext.c	config: use find_config_tree_array for all arrays	2015-07-15 10:52:23 +02:00
toolcontext.h	vgchange/lvchange: enforce the shared VG lock from lvmlockd	2015-07-17 15:35:34 -05:00