Linux RAID subsystem development
 help / color / mirror / Atom feed
From: "Ionut Nistor" <ionut@modulo.ro>
To: Lars Marowsky-Bree <lmb@suse.de>,
	Paul Clements <Paul.Clements@SteelEye.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Multipath problem in a SAN enviromnent
Date: Thu, 12 Jun 2003 13:51:06 +0300	[thread overview]
Message-ID: <007c01c330d0$86dda7b0$0cc7e7c1@EEL> (raw)
In-Reply-To: 20030612100423.GA14106@marowsky-bree.de

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

  reply	other threads:[~2003-06-12 10:51 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   ` Multipath problem in a SAN enviromnent Ionut Nistor
2003-06-11 17:59     ` Paul Clements
2003-06-12  6:28       ` Ionut Nistor
2003-06-12 10:04   ` Lars Marowsky-Bree
2003-06-12 10:51     ` Ionut Nistor [this message]
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='007c01c330d0$86dda7b0$0cc7e7c1@EEL' \
    --to=ionut@modulo.ro \
    --cc=Paul.Clements@SteelEye.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=lmb@suse.de \
    /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