All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lars Marowsky-Bree <lmb@suse.de>
To: linux-raid@vger.kernel.org
Subject: Re: Does mdadm work on active/passive arrays
Date: Mon, 25 Apr 2005 23:22:29 +0200	[thread overview]
Message-ID: <20050425212229.GY32085@marowsky-bree.de> (raw)
In-Reply-To: <426D5333.4080502@bms.com>

On 2005-04-25T16:29:39, Anu Matthew <anu.matthew@bms.com> wrote:

> Just a small question about creating multipath devices using mdadm:
> 
> Does it support Active/Passive Arrays like the Clariion?

This is not a function of mdadm, but of the md multipath code in the
kernel. The short answer is: "No". 

md multipath is not being actively developed and extended in 2.6 any
longer.

However, there is hope. The Device Mapper multipath module _does_
support the EMC CLARiiON CX-family of arrays quite well (in fact, I'm
developing with one). At least in the latest udm patchsets by Alasdair,
and in combination with the multipath-tools userspace package.

The multipath support in SLES9 SP2 will be based on this, and to my
knowledge also that in RHEL4 U1, but I can only guess about that ;-)

The latest tools are basically zero config on those arrays: Just start
it and it'll do the right things. For SLES9, we'll publish a Support
Database Article in time with the release. (Because obviously the actual
integration into the distribution differs slightly.)

You can find more information about DM MPIO at
http://sources.redhat.com/dm/.

That said:

> I am using mdadm  v1.11.0, and the devices return no UUID when queried 
> using mdadm -D --scan.

No wonder; mdadm tries to read the md superblock of the disk, which is
not possible for a passive path on an EMC CX. You first need to send the
SCSI trespass command to re-bind the Logical Unit to that Service
Processor. (Which at the same time makes it inaccessible on the other
SP...) mdadm and md multipath don't know about that and can't handle it.

> BTW, I am using qla2300 modules with options scsi_mod max_scsi_luns=255 
> scsi_allow_ghost_devices=1.

FWIW, I also recommend
options qla2xxx qlport_down_retry=1 ql2xfailover=0 ql2xretrycount=5
to faciliate fast switch-over in case a path fails.

At least it seems to work fine during my testing so far ;-)


Sincerely,
    Lars Marowsky-Brée <lmb@suse.de>

-- 
High Availability & Clustering
SUSE Labs, Research and Development
SUSE LINUX Products GmbH - A Novell Business

-
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:[~2005-04-25 21:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-25 20:29 Does mdadm work on active/passive arrays Anu Matthew
2005-04-25 21:22 ` Lars Marowsky-Bree [this message]

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=20050425212229.GY32085@marowsky-bree.de \
    --to=lmb@suse.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.