Re: auto_activation_volume_list in lvm.conf not honored

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Peter,

as i said, we have master/slave setup _without_ concurrent write/read. So i do not see a reason why i should take care of locking as only one node is activating the volume group at the same time.

That should be fine - right?

Stefan
-----Ursprüngliche Nachricht-----
> Von:Zdenek Kabelac <zkabelac@redhat.com>
> 
> If you are working with 'shared' storage and manipulating  same VG from 
> multiple nodes (i.e. activation) - it's not so easy to go without really good 
> locking manager.
> 
> If you don't like clvmd - maybe you could take a look at lvmlockd & sanlock.
> 
> But you should be aware there are NOT many people who are able to ensure 
> correct locking of lvm2 commands -  it's really not just 'master/slave'.
> There are big number of error cases which do not proper locking around
> the whole cluster.

_______________________________________________
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/




[Index of Archives]     [Gluster Users]     [Kernel Development]     [Linux Clusters]     [Device Mapper]     [Security]     [Bugtraq]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]

  Powered by Linux