From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lars Marowsky-Bree Subject: Re: Multipath problem in a SAN enviromnent Date: Thu, 12 Jun 2003 12:04:23 +0200 Sender: linux-raid-owner@vger.kernel.org Message-ID: <20030612100423.GA14106@marowsky-bree.de> References: <02d201c33023$13fd45a0$3351960a@EEL> <3EE7585E.45D851CE@SteelEye.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Content-Disposition: inline In-Reply-To: <3EE7585E.45D851CE@SteelEye.com> To: Paul Clements , Ionut Nistor Cc: linux-raid@vger.kernel.org List-Id: linux-raid.ids On 2003-06-11T12:27:10, Paul Clements said: > One way to get around this problem is to use non-persistent superbloc= ks > for your arrays and just re-create them at bootup time by calling mkr= aid > (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=E9e --=20 SuSE Labs - Research & Development, SuSE Linux AG =20 "If anything can go wrong, it will." "Chance favors the prepared (mind)= =2E" -- Capt. Edward A. Murphy -- Louis Pasteur - To unsubscribe from this list: send the line "unsubscribe linux-raid" i= n the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html