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

Zdenek Kabelac zdenek.kabelac at gmail.com
Fri Nov 25 09:30:39 UTC 2016

Dne 25.11.2016 v 10:17 Stefan Bauer napsal(a):
> 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?

Nope it's not.

Every i.e. activation  DOES validation of all resources and takes ACTION when 
something is wrong.

Sorry, but there is NO way to do this properly without locking manager.

Although many lvm2 users always do try to be 'innovative' and try to use in 
lock-less way - this seems to work most of the time - till the moment some
disaster happens - then just lvm2 is blamed about data loss..

Interestingly they never tried to think why we invested so much time into 
locking manager when there is such 'easy-fix' in their eyes...

IMHO lvmlockd is relatively 'low-resource/overhead' solution worth to be 
explored if you don't like clvmd...



More information about the linux-lvm mailing list