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

2016-11-25 Thread Stefan Bauer
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

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

2016-11-25 Thread Zdenek Kabelac
Dne 24.11.2016 v 15:02 Stefan Bauer napsal(a): Hi Peter, now all make sense. On this ubuntu machine upstartd with udev is taking care of vgchange. After some digging, /lib/udev/rules.d/85-lvm2.rules shows, that vgchange is only executed with -a y We will test this on weekend but I'm certain

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

2016-11-24 Thread Stefan Bauer
Its already gone in newer releases of Ubuntu. They replaced upstartd with sytemd. The systemd scripts look sane and use -aay. Stefan -Ursprüngliche Nachricht- > Von:Peter Rajnoha > SUBSYSTEM=="block", ACTION=="add|change", ENV{ID_FS_TYPE}="lvm*|LVM*", >

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

2016-11-24 Thread Stefan Bauer
ovember 2016 14:39 > An: linux-lvm@redhat.com > CC: s...@plzk.de > Betreff: Re: [linux-lvm] auto_activation_volume_list in lvm.conf not honored > > On 11/24/2016 01:21 PM, Stefan Bauer wrote: > > hi folks, > > > > howto avoid pvescan to initialize lvm volume gro

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

2016-11-24 Thread Peter Rajnoha
On 11/24/2016 02:38 PM, Peter Rajnoha wrote: > On 11/24/2016 01:21 PM, Stefan Bauer wrote: >> hi folks, >> >> howto avoid pvescan to initialize lvm volume groups on startup (it's for a >> cluster setup)? auto_activation_volume_list was filled with the remaining >> VGs we want to setup. Manually

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

2016-11-24 Thread Stefan Bauer
hi folks, howto avoid pvescan to initialize lvm volume groups on startup (it's for a cluster setup)? auto_activation_volume_list was filled with the remaining VGs we want to setup. Manually it does what it should /sbin/lvm pvescan --config 'activation { auto_activation_volume_list = "vg2" }'