[ClusterLabs] volume group won't start in a nested DRBD setup

[Jean-Francois Malouin]

* Jean-Francois Malouin <Jean-Francois.Malouin at bic.mni.mcgill.ca> [20191029 09:49]:
> * Roger Zhou <ZZhou at suse.com> [20191029 06:18]:
> > 
> > On 10/29/19 12:30 PM, Andrei Borzenkov wrote:
> > >> Oct 28 14:42:56 node2 LVM(p_lvm_vg0)[8775]: INFO: Activating volume group vg0
> > >> Oct 28 14:42:56 node2 LVM(p_lvm_vg0)[8775]: INFO:  Reading all physical volumes. This may take a while... Found volume group "vmspace" using metadata type lvm2 Found volume group "freespace" using metadata type
> > >>   lvm2 Found volume group "vg0" using metadata type lvm2
> > >> Oct 28 14:42:56 node2 LVM(p_lvm_vg0)[8775]: INFO:  0 logical volume(s) in volume group "vg0" now active
> > > Resource agent really does just "vgchange vg0". Does it work when you
> > > run it manually?
> > > 
> > 
> > Agree with Andrei.
> 
> Yes, it does. 
> > 
> > > 
> > >> Oct 28 14:42:56 node2 LVM(p_lvm_vg0)[8775]: ERROR: LVM Volume vg0 is not available (stopped)
> > >> Oct 28 14:42:56 node2 LVM(p_lvm_vg0)[8775]: ERROR: LVM: vg0 did not activate correctly
> > >> Oct 28 14:42:56 node2 pacemaker-execd[27054]:  notice: p_lvm_vg0_start_0:8775:stderr [   Configuration node global/use_lvmetad not found ]
> > 
> > This error indicates the root cause is related to lvmetad. Please check 
> > lvmetad, eg.
> > 
> > systemctl status lvm2-lvmetad
> > grep use_lvmetad /etc/lvm/lvm.conf
> > 
> > Check your lvm2 version and google its workaround/fix accordingly.
> 
> That was my hunch too. This is on Debian/buster and the lvm.conf is the
> original one from the initial install except for the configuration option
> devices/filter that added:
> 
>      filter = [ "a|/dev/drbd.*|", "a|/dev/md.*|", "a|/dev/md/.*|", "r|.*|" ]
>      write_cache_state = 0
> 
> and the configuration option devices/global_filter:
> 
>     global_filter = [ "a|/dev/drbd.*|", "a|/dev/md.*|", "a|/dev/md/.*|", "r|.*|" ]
> 
> There was no 'use_lvmetad' option present initially but I have add it in the global section.
>     use_lvmetad = 0
> 
> And lvm2-lvmetad is not a unit listed under systemd...
> 
>     systemctl status lvm2-lvmetad
>     Unit lvm2-lvmetad.service could not be found.

I had a second go at this earlier this morning and it seems that I might have
NOT enabled 'filter' and 'global_filter' at the same time, or with 'use_lvmetad = 0' 
too at the same time as right now the volume group vg0 is running correctly and
I can move it around no problem.

I'm reviewing all this as I'm a bit baffled...

thanks for all your input,
jf

> 
> thanks,
> jf
> 
> > 
> > Cheers,
> > Roger
> > 
> > >> Oct 28 14:42:56 node2 pacemaker-execd[27054]:  notice: p_lvm_vg0_start_0:8775:stderr [ ocf-exit-reason:LVM: vg0 did not activate correctly ]
> > >> Oct 28 14:42:56 node2 pacemaker-controld[27057]:  notice: Result of start operation for p_lvm_vg0 on node2: 7 (not running)
> > >> Oct 28 14:42:56 node2 pacemaker-controld[27057]:  notice: node2-p_lvm_vg0_start_0:77 [   Configuration node global/use_lvmetad not found\nocf-exit-reason:LVM: vg0 did not activate correctly\n ]
> > >> Oct 28 14:42:56 node2 pacemaker-controld[27057]:  warning: Action 42 (p_lvm_vg0_start_0) on node2 failed (target: 0 vs. rc: 7): Error
> > >> Oct 28 14:42:56 node2 pacemaker-controld[27057]:  notice: Transition 602 aborted by operation p_lvm_vg0_start_0 'modify' on node2: Event failed
> >