Lidong Zhong 39e6c4f749 lvmlockd: purge the lock resources left in previous lockspace ... If lvmlockd in cluster is killed accidently or any other reason, the lock resources will become orphaned in the VG lockspace. When the cluster manager tries to restart this daemon, the LVs will probably become inactive because of resource schedule policy and thus the lock resouce will be omited during the adoption process. This patch will try to purge the lock resources left in previous lockspace, so the following actions can work again.		2022-10-07 09:45:57 -05:00
..
.gitignore	gitignore: Update for in-place build.	2015-07-27 13:18:35 +01:00
lvmlockctl.c	cov: ensuring buffer is zeroed	2021-09-21 21:03:47 +02:00
lvmlockd-client.h	cleanup: matching declaration order	2020-09-01 17:57:50 +02:00
lvmlockd-core.c	lvmlockd: purge the lock resources left in previous lockspace	2022-10-07 09:45:57 -05:00
lvmlockd-dlm.c	lvmlockd: purge the lock resources left in previous lockspace	2022-10-07 09:45:57 -05:00
lvmlockd-idm.c	cleanup: free already does NULL check	2021-09-15 15:24:56 +02:00
lvmlockd-internal.h	lvmlockd: purge the lock resources left in previous lockspace	2022-10-07 09:45:57 -05:00
lvmlockd-sanlock.c	lvmlockd: return error from vgcreate init_vg_sanlock	2022-04-08 11:34:04 -05:00
Makefile.in	lvmlockd: idm: Introduce new locking scheme	2021-05-20 16:00:59 -05:00