David Teigland 2d1fe38d84 lvmlockd: use 4K sector size when any dev is 4K ... When either logical block size or physical block size is 4K, then lvmlockd creates sanlock leases based on 4K sectors, but the lvm client side would create the internal lvmlock LV based on the first logical block size it saw in the VG, which could be 512. This could cause the lvmlock LV to be too small to hold all the sanlock leases. Make the lvm client side use the same sizing logic as lvmlockd.		2020-05-11 13:14:55 -05:00
..
.exported_symbols	Pre-release cleanups.	2009-05-21 03:04:52 +00:00
file_locking.c	locking: unify global lock for flock and lockd	2019-04-29 13:01:05 -05:00
locking_types.h	Implement lock-override options without locking type	2018-06-07 16:17:04 +01:00
locking.c	pvcreate,pvremove: fix reacquiring global lock after prompt	2019-11-26 14:34:43 -06:00
locking.h	pvcreate,pvremove: fix reacquiring global lock after prompt	2019-11-26 14:34:43 -06:00
lvmlockd.c	lvmlockd: use 4K sector size when any dev is 4K	2020-05-11 13:14:55 -05:00
lvmlockd.h	build: fix compilation without lvmlockd	2019-05-03 13:17:22 +02:00