[linux-lvm] auto_activation_volume_list in lvm.conf not honored

Stefan Bauer sb at plzk.de
Fri Nov 25 09:17:02 UTC 2016

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?

-----Ursprüngliche Nachricht-----
> Von:Zdenek Kabelac <zkabelac at 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.

More information about the linux-lvm mailing list