From: "Ionut Nistor" <ionut@modulo.ro>
To: Paul Clements <Paul.Clements@SteelEye.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Multipath problem in a SAN enviromnent
Date: Wed, 11 Jun 2003 19:45:46 +0300 [thread overview]
Message-ID: <038101c33038$e8a6e760$3351960a@EEL> (raw)
In-Reply-To: 3EE7585E.45D851CE@SteelEye.com
Yes, you would get around it. But the main point of the superblock (i.e.
disk membership/status/array uuid) is to be able to identify the disks in an
array if devices allocation changes.
There must be a *safe* way of identifying the devices.
-
Ionut
----- Original Message -----
From: "Paul Clements" <Paul.Clements@SteelEye.com>
To: "Ionut Nistor" <ionut@modulo.ro>
Cc: <linux-raid@vger.kernel.org>
Sent: Wednesday, June 11, 2003 7:27 PM
Subject: Re: Multipath problem in a SAN enviromnent
> Ionut Nistor wrote:
>
> > So scsi1, bus0, target0, lun2 is now 8,16 instead of 8,32
> >
> > However, the raid superblock still has 8,32 in it - this confuses
> > multipath
>
> 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.
>
> --
> Paul
>
next prev parent reply other threads:[~2003-06-11 16:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-11 14:09 Multipath problem in a SAN enviromnent Ionut Nistor
2003-06-11 15:49 ` Dominik Kubla
2003-06-11 16:47 ` Ionut Nistor
2003-06-11 16:27 ` Paul Clements
2003-06-11 16:42 ` Moving Disks [Re: Multipath problem in a SAN enviromnent] Gordon Henderson
2003-06-11 16:45 ` Ionut Nistor [this message]
2003-06-11 17:59 ` Multipath problem in a SAN enviromnent Paul Clements
2003-06-12 6:28 ` Ionut Nistor
2003-06-12 10:04 ` Lars Marowsky-Bree
2003-06-12 10:51 ` Ionut Nistor
2003-06-12 14:52 ` Paul Clements
2003-06-13 8:12 ` Ionut Nistor
2003-06-18 10:21 ` Lars Marowsky-Bree
2003-06-19 15:25 ` Ionut Nistor
2003-06-11 19:24 ` Luca Berra
2003-06-12 6:35 ` Ionut Nistor
2003-06-11 19:34 ` Paul Clements
2003-06-12 6:37 ` Ionut Nistor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='038101c33038$e8a6e760$3351960a@EEL' \
--to=ionut@modulo.ro \
--cc=Paul.Clements@SteelEye.com \
--cc=linux-raid@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).