Dne 28.8.2017 v 14:41 Kalyana sundaram napsal(a):
We have a shared iscsi disk at all our boxes, with one vg. We are using clvm
to manage locks to create extend activate delete list.
CLVM is tedious to manage especially especially due to reboot if locking is
struck somewhere. Instead we are thinking of modifying file_locking.c to get
lock with distributed store like zookeeper or redis and on success run the
above command, on failure backoff and try again
The external ocking code will sit at _file_lock_resource, case LCK_VG.
Do you think its risky. Is there some other way people handle it?
Hi
Have you considered usage of 'lvmlockd' and it's sanlock interface
(where locks are maintained on shared storage device).
Regards
Zdenek
_______________________________________________
linux-lvm mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
