David Teigland bf60cb4da2 lvmlockd: avoid lockd_vg for local VGs ... Previously, a command would call lockd_vg() for a local VG, which would go to lvmlockd, which would send back ENOLS, and the command would not care when it saw the VG was local. The pointless back-and-forth to lvmlockd for local VGs can be avoided by checking the VG lock_type in lvmcache (which label_scan now saves there; this wasn't the case back when the original lockd_vg logic was added.) If the lock_type saved during label_scan indicates a local VG, then the lockd_vg step is skipped.		2024-06-27 13:29:03 -05:00
..
.exported_symbols	Pre-release cleanups.	2009-05-21 03:04:52 +00:00
file_locking.c	refactor: update dm_strncpy to _dm_strncpy	2024-04-04 19:38:21 +02:00
locking_types.h	Implement lock-override options without locking type	2018-06-07 16:17:04 +01:00
locking.c	refactor: update dm_strncpy to _dm_strncpy	2024-04-04 19:38:21 +02:00
locking.h	backup: automatically store data on vg_unlock	2021-06-09 14:56:13 +02:00
lvmlockd.c	lvmlockd: avoid lockd_vg for local VGs	2024-06-27 13:29:03 -05:00
lvmlockd.h	lvmlockd: Fix syntax error in previous commit	2023-01-11 13:34:38 +01:00