Re: Lvm Strange Problem

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

 



On Mon, 11 Oct 2010, Jörg Stephan wrote:

> > It seems pretty clear that all your servers have both a snapshot and a
> > live LV.  At power up, they search for their disk and randomly find
> > either the live or the snapshot first.  You need to take the snapshots 
> > out of the search path.
> >
> well, mostly the snapshot was removed some days after they were made.
> Also the snapshots had of course different names, how could it be that
> they were used? And even if this, why are all machines with the failure
> bound to the same date?

I believe your problem is with your SAN, not LVM (you did mention using iSCSI).
I'm talking about SAN snapshots, not LVM snapshots (although the SAN server 
could very well use LVM underneath).  The SAN volumes have no names, just
LUNs.  At boot, they are searched for a matching UUID, just like directly
attached physical volumes.  When taking a SAN snapshot (clone), the UUID
of the clone is the same as the original, whether a filesystem or VG is
on the SAN LUN.

-- 
	      Stuart D. Gathman <stuart@bmsi.com>
    Business Management Systems Inc.  Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flammis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.
_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

[Index of Archives]     [Gluster Users]     [Kernel Development]     [Linux Clusters]     [Device Mapper]     [Security]     [Bugtraq]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]

  Powered by Linux