[linux-lvm] Full DRDB device on LVM is now unusable

[Lars Ellenberg]

On Wed, Feb 05, 2014 at 05:11:35PM -0000, Seb A wrote:
> > -----Original Message-----
> > From: linux-lvm-bounces at redhat.com On Behalf Of Zdenek 
> > Kabelac zkabelac-at-redhat.com
> > Sent: 30 January 2014 11:02
> > Subject: Re: [linux-lvm] Full DRDB device on LVM is now unusable
> > 
> > As a follow-up of irc discussion.
> > 
> > 
> > incorrect  filter rules were set.
> > 
> > 
> > For drbd its mandatory to let lvm2 command see only those 
> > devices which are 
> > supposed to be used.
> > 
> > Reference to drbd lvm nesting guide:
> > http://www.drbd.org/users-guide-8.3/s-nested-lvm.html
> > 
> > Rule #1 - set an appropriate 'filter' is very important.
> > 
> > For activation of nested LV  lvm must not see drbd origin nodes!
> > 
> > 
> > Zdenek
> 
> Many thanks for your help Zdenek.  As you know, we were able to able to get
> the volume mounted on 'Openfiler2' by changing the LVM filter rules.  What
> was very strange, is that they had been working fine for over 2 years.  And
> that fixing the rules prevented the volume being displayed in the output
> from lvscan and lvdisplay.  Updating the lvm2 package fixed this display
> though - but only on Openfiler2.  After our conversation, I made the same
> changes to 'Openfiler1' and it was not able to see the volumes in lvscan and
> lvdisplay - until I reverted the change to filter rules (but kept the newer
> lvm2 package) to the one I had been using for years.  So, it is still a bit
> of a mystery.  But the main thing is that it is working now - and I know
> where to look if it happens again.

Now, if the filter is correct,
LVM won't see the VG as long as DRBD is "Secondary"
(unless LVM takes the info from some stale cache file,
which I have seen as well).

You have to promote DRBD first,
only then (potentially re-scan, depending on
exact LVM setup, and) activate the VG.

-- 
: Lars Ellenberg
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting http://www.linbit.com