From: Benjamin Marzinski <bmarzins@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: Clariion CX600 automatic failback support
Date: Mon, 7 Nov 2005 13:25:10 -0600 [thread overview]
Message-ID: <20051107192510.GC26529@phlogiston.msp.redhat.com> (raw)
In-Reply-To: <C2EEB4E538D3DC48BF57F391F422779321AD96@SRMANNING.eng.emc.com>
On Wed, Nov 02, 2005 at 04:32:06PM -0500, goggin, edward wrote:
> On Date: Mon, 31 Oct 2005 08:58:06 -0500
> Brian Long <brilong@cisco.com> wrote
>
> >
> > On Wed, 2005-10-26 at 15:37 -0400, Phil Lowden (plowden) wrote:
> > > I'm using LVM2 with device-mapper-multipath 0.4.5 on GA
> > RHEL 4 update 2
> > > release, kernel version 2.6.9-22.ELsmp. Storage is 4 Clariion CX600
> > > LUNs,
> > > 2 with a primary path on SP A and 2 on SP B. HBAs are QLA3240 with
> > > firmware 3.03.15 IPX and the RedHat-distributed driver version
> > > 8.01.00b5-rh2.
> > >
> > > When I disrupt one path by disabling a host or SP switch port,
> > > failover works great but failback doesn't happen automatically
> > > with the current config (below). By this I mean
> > > when the connection to e.g. SP B is restored, all
> > > 4 LUNs stay trespassed to SP A. Is this by design?
> > > Or is there support for automatic failback, i.e.
> > > I/O is paused and a trespass is issued to restore
> > > the 2 SP B LUNs to their primary paths?
> > >
> > > Of course manual failback is possible, but without
> > > quiescing I/O I found I was able to munge my LVM2
> > > objects up quite nicely. Manual failback with quiesced
> > > I/O is fine.
> >
> > No one has automatic failback working on Clarrion storage?
>
> Unfortunately, this doesn't just work "out of the box" yet.
>
> You need to setup a default failback setting of immediate in the
> /etc/multipath.conf configuration file, ...
>
> defaults {
> failback immediate
> }
>
> ... or selectively set the failback setting to immediate in the
> multipath config file for each EMC CLARiiON logical unit
>
> multipaths {
> multipath {
> wwid 360061 ...
> failback immediate
> }
> ...
> }
>
> Setting this attribute value for the entire EMC CLARiiON class of
> devices via the multipath config file "device" attribute doesn't
> work because of a bug (mpp->hwe field is never set for multipathd)
> in the multipathd code which is patched to work by the single line
> patch below. Due to the same bug, a patch I submitted many weeks
> ago to libmultipath/hwtable.c to setup the default failback policy
> for EMC CLARiiON to immediate also does not work.
>
> Once the distributors pick up both this single line change and the
> change in hwtable.c, immediate path group failback for CLARiiON
> will just work.
These changes are both in the RHEL4 U3 code.
> -------------------------------------------------------------------
> diff --git a/multipathd/main.c b/multipathd/main.c
> --- a/multipathd/main.c
> +++ b/multipathd/main.c
> @@ -146,6 +146,7 @@ adopt_paths (struct vectors * vecs, stru
> if (!strncmp(mpp->wwid, pp->wwid, WWID_SIZE)) {
> condlog(4, "%s ownership set", pp->dev_t);
> pp->mpp = mpp;
> + mpp->hwe = pp->hwe;
> }
> }
> }
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
next prev parent reply other threads:[~2005-11-07 19:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-02 21:32 Clariion CX600 automatic failback support goggin, edward
2005-11-03 13:58 ` Christophe Varoqui
2005-11-07 19:25 ` Benjamin Marzinski [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-11-06 18:29 goggin, edward
2005-11-04 19:36 goggin, edward
2005-11-04 20:55 ` Christophe Varoqui
2005-11-05 0:03 ` Bernd Zeimetz
2005-11-05 12:26 ` Christophe Varoqui
2005-11-10 19:24 ` Bernd Zeimetz
2005-11-03 18:16 goggin, edward
2005-11-03 20:55 ` Brian Long
2005-11-03 22:00 ` Bernd Zeimetz
2005-11-04 8:19 ` Bernd Zeimetz
2005-11-04 9:47 ` Christophe Varoqui
2005-10-26 19:37 Phil Lowden (plowden)
2005-10-31 13:58 ` Brian Long
2005-10-31 14:02 ` Bernd Zeimetz
2005-10-31 14:07 ` Christophe Varoqui
2005-10-31 15:51 ` Brian Long
2005-10-31 16:06 ` Christophe Varoqui
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=20051107192510.GC26529@phlogiston.msp.redhat.com \
--to=bmarzins@redhat.com \
--cc=dm-devel@redhat.com \
/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.