[linux-lvm] Distributed Locking of LVM
kalyanceg at gmail.com
Thu Aug 31 06:32:11 UTC 2017
Thanks all people
I understand reboot/fencing is mandatory
I hope the visibility might be better in external locking tool like redis
With lvmlockd I find no deb available for ubuntu, and documentations for
clvm to handle an issue is difficult to find
Could somebody redirect me for a good documentation on clvm?
Let me compile lvmlockd and give it a shot
On Tue, Aug 29, 2017 at 9:53 PM, David Teigland <teigland at redhat.com> wrote:
> On Tue, Aug 29, 2017 at 11:25:19AM +0200, Zdenek Kabelac wrote:
> > 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
> > > is struck somewhere. Instead we are thinking of modifying
> > > 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).
> And lvmlockd can use different lock managers. Currently it supports
> sanlock (where the locks are kept in the VG's storage and networking is
> not used), or the dlm (which uses the network and requires corosync). You
> also could try adding another lock manager option to lvmlockd.
> See here for more info:
> I think people will find lvmlockd works much better than clvm.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the linux-lvm