David Teigland 75886f59e4 lvmlockd: make lockstart wait for existing start ... If there are two independent scripts doing: vgchange --lockstart vg lvchange -ay vg/lv The first vgchange to do the lockstart will wait for the lockstart to complete before returning. The second vgchange to do the lockstart will see that the start is already in progress (from the first) and will do nothing. This means the second does not wait for any lockstart to complete, and moves on to the lvchange which may find the lockspace still starting and fail. To fix this, make the vgchange lockstart command wait for any lockstart's in progress to complete.		2019-01-31 09:38:50 -06:00
..
.gitignore	gitignore: Update for in-place build.	2015-07-27 13:18:35 +01:00
lvmlockctl.c	lvmlockctl: fix check for failing close	2017-08-25 14:20:59 +02:00
lvmlockd-client.h	lvmlockd: override unknown lock manager error numbers	2017-11-17 10:59:12 -06:00
lvmlockd-core.c	lvmlockd: make lockstart wait for existing start	2019-01-31 09:38:50 -06:00
lvmlockd-dlm.c	clean: drop unneeded -1 for snprintf	2018-02-12 22:14:25 +01:00
lvmlockd-internal.h	lvmlockd: improve error message about missing global lock	2016-07-25 14:49:01 -05:00
lvmlockd-sanlock.c	sanlock: set proper return value	2018-02-19 16:44:10 +01:00
Makefile.in	build: properly track source file for lmvlockctl	2018-05-12 18:05:50 +02:00