[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

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



> -----Original Message-----
> From: linux-lvm-bounces 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.

Kind regards, 

Seb A


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]