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
..
clvmd	scan: reopen RDWR during rescan	2018-06-26 12:15:43 -05:00
cmirrord	build: add -D_FILE_OFFSET_BITS=64	2018-05-02 18:40:38 +01:00
dmeventd	dmeventd: lvm2 plugin uses envvar registry	2018-09-05 14:39:14 +02:00
dmfilemapd	coverity: missing free on error path	2018-02-28 21:05:18 +01:00
lvmdbusd	python: use // for integer division	2018-05-18 16:25:44 +02:00
lvmetad	Remove lvm1 and pool disk formats	2018-04-30 16:55:02 -05:00
lvmlockd	lvmlockd: make lockstart wait for existing start	2019-01-31 09:38:50 -06:00
lvmpolld	makefiles: fixing linking	2017-08-01 11:53:30 +02:00
Makefile.in	daemons: add dmfilemapd	2017-03-09 18:50:15 +00:00