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
..
.gitignore	gitignore: Update for in-place build.	2015-07-27 13:18:35 +01:00
lvmlockctl.c	lvmlockctl: update command descriptions and add logging	2015-09-04 11:05:13 -05:00
lvmlockd-client.h	lvmlockd: improve VG removal for lock_type dlm	2015-08-27 10:27:24 -05:00
lvmlockd-core.c	lvmlockd: unlock lv if command fails before lock completes	2015-09-16 15:56:54 -05:00
lvmlockd-dlm.c	lvmlockd: prevent vgremove of dlm VG while lockspace is used	2015-09-11 14:12:13 -05:00
lvmlockd-internal.h	lvmlockd: unlock lv if command fails before lock completes	2015-09-16 15:56:54 -05:00
lvmlockd-sanlock.c	lvmlockd: check all variations of lvb values	2015-09-10 09:47:26 -05:00
Makefile.in	lvmlockd: Drop -lrt now handled by configure.	2015-07-27 14:53:08 +01:00