David Teigland b7410c95cf lvmlockd: unlock lv if command fails before lock completes ... If lvmlockd acquires an lv lock for a command, but the command exits before the reply, then the command has not activated the lv and lvmlockd should unlock it. This only applies when the lv was not already locked. (There will always be a chance that the lv lock is held while the lv is not active, i.e. if the command fails in the small window between getting the lv lock and before doing the activation. In that case, rerunning the activation command corrects the inconsistency.) This commit helps by automatically clearing the inconsistency (lv locked by not activated) in the most common case when the lv lock operation is slow to complete and the command is canceled by the user. This commit also adds and cleans up references to the client id in a bunch of log messages, which is useful to follow processing on each independent lock request.		2015-09-16 15:56:54 -05:00
..
clvmd	cleanup: move var declaration	2015-08-18 16:05:04 +02:00
cmirrord	style: Standardise some error paths.	2015-09-05 23:56:30 +01:00
dmeventd	dmeventd: reorder mempool allocation	2015-09-03 23:34:36 +02:00
lvmetad	makefiles: distclean missing files	2015-09-11 21:52:27 +02:00
lvmlockd	lvmlockd: unlock lv if command fails before lock completes	2015-09-16 15:56:54 -05:00
lvmpolld	lvmpolld: make lvpoll error messages visible	2015-09-02 17:24:26 +02:00
Makefile.in	Add lvmlockd	2015-07-02 15:42:26 -05:00