Re: Multipath problem in a SAN enviromnent

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

 



Hello Lars,

Are these changes documented?
Is there a changelog?
In which official kernel has the patch been merged?
Is there a separate patch I can apply to 2.4.18 vanilla?

Thanks a lot,
Ionut

----- Original Message ----- 
From: "Lars Marowsky-Bree" <lmb@suse.de>
To: "Paul Clements" <Paul.Clements@SteelEye.com>; "Ionut Nistor"
<ionut@modulo.ro>
Cc: <linux-raid@vger.kernel.org>
Sent: Thursday, June 12, 2003 1:04 PM
Subject: Re: Multipath problem in a SAN enviromnent


> On 2003-06-11T12:27:10,
>    Paul Clements <Paul.Clements@SteelEye.com> said:
>
> > One way to get around this problem is to use non-persistent superblocks
> > for your arrays and just re-create them at bootup time by calling mkraid
> > (or mdadm) after you've correctly identified (using WWID or similar)
> > which devices belong to each particular raid set.
>
> The patches I did to multipath in 2.4 went even further: As the md
> superblock - this_disk etc - has little meaning for multipath, as they
> are all identical, I made the assembly based entirely on the UUID,
> ignoring the device nodes completely.
>
>
> Sincerely,
>     Lars Marowsky-Brée <lmb@suse.de>
>
> -- 
> SuSE Labs - Research & Development, SuSE Linux AG
>
> "If anything can go wrong, it will." "Chance favors the prepared (mind)."
>   -- Capt. Edward A. Murphy            -- Louis Pasteur
>

-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux