On 2017-08-28 08:41 AM, Kalyana sundaram wrote: > 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? I think you're trying to work around a problem, instead of solving it. The only time locking blocks with DLM is if a node entered an unknown state and fencing wasn't setup or failed (in which case hanging is the least bad option available). A lot of thought and design went into DLM / clvmd. I would be cautious trying to reinvent a wheel this complex. Instead, do you have any indication why blocking occurs? Do you have fencing setup and working? What cluster stack/version/OS are you using? You might want to post on the clusterlabs list, too. Users: .... http://lists.clusterlabs.org/mailman/listinfo/users Developers: http://lists.clusterlabs.org/mailman/listinfo/developers -- Digimer Papers and Projects: https://alteeve.com/w/ "I am, somehow, less interested in the weight and convolutions of Einstein’s brain than in the near certainty that people of equal talent have lived and died in cotton fields and sweatshops." - Stephen Jay Gould _______________________________________________ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
