From: Hannes Reinecke <hare@suse.de>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: rdac priority checker changing priorities
Date: Thu, 30 Apr 2009 08:25:02 +0200 [thread overview]
Message-ID: <49F9443E.7040109@suse.de> (raw)
In-Reply-To: <9ad205140904291534j4cc1a71aq3b4a0e308f1687bd@mail.gmail.com>
Hi Lucas,
Lucas Brasilino wrote:
> Hi
>
> I don't know if I'm misundertanding something. I've got an DS4700 and I'm
> switching from RDAC[1] to multipath, since it's natively supported in
> the distribution I use
> here (SLES 10 SP2).
>
> Since RDAC[1] works perfect, I'm trying to use 'rdac' priority in multipath.
>
> My /etc/multiconf.conf is quite tiny, since I'm building it step-by-step :-) :
>
> blacklist {
> devnode "^sda[0-9]*"
> }
>
> defaults {
> user_friendly_names yes
> prio rdac
> path_checker tur
> }
>
> multipaths {
> multipath {
> wwid 3600a0b8000327b900000107549f85224
> alias mpath0
> }
> }
>
> I think that using 'prio rdac' makes multipath to use 'mpath_prio_rdac' tool.
>
> # multipath -v2 -ll
> mpath0 (3600a0b8000327b900000107549f85224) dm-0 IBM,1814 FAStT
> [size=140G][features=1 queue_if_no_path][hwhandler=1 rdac]
> \_ round-robin 0 [prio=6][active]
> \_ 9:0:0:0 sdb 8:16 [active][ready]
> \_ round-robin 0 [prio=1][enabled]
> \_ 10:0:0:0 sdc 8:32 [active][ghost]
>
> So the first path has priority 6, as I can confirm:
>
> # mpath_prio_rdac /dev/sdb
> 6
> # mpath_prio_rdac /dev/sdc
> 1
>
> After the first path (prio=6) failure I get:
>
> # multipath -v2 -ll
> sdb: rdac prio: inquiry command indicates error
> mpath0 (3600a0b8000327b900000107549f85224) dm-0 IBM,1814 FAStT
> [size=140G][features=1 queue_if_no_path][hwhandler=1 rdac]
> \_ round-robin 0 [prio=0][enabled]
> \_ 9:0:0:0 sdb 8:16 [failed][faulty]
> \_ round-robin 0 [prio=1][enabled]
> \_ 10:0:0:0 sdc 8:32 [active][ghost]
>
> Ok.. working great, activating the second path. But after the faulty
> path is restored:
>
> # multipath -v2 -ll
> mpath0 (3600a0b8000327b900000107549f85224) dm-0 IBM,1814 FAStT
> [size=140G][features=1 queue_if_no_path][hwhandler=1 rdac]
> \_ round-robin 0 [prio=2][enabled]
> \_ 9:0:0:0 sdb 8:16 [active][ghost]
> \_ round-robin 0 [prio=5][active]
> \_ 10:0:0:0 sdc 8:32 [active][ready]
>
> Second path is now priority!!! And of course does not fails back! By
> the way, my LUN is configured in
> DS4700 in sort a way that the first path *is* the path to preferred controller.
>
> I think path priorities should not change. If so first path goes back
> to 'active' status.
> Am I misunderstanding something ? Or messing things up?
>
You are using an old version of multipathing for SLES10 SP2.
This had a bug triggering priority inversion on RDAC.
Please update to the latest version.
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Markus Rex, HRB 16746 (AG Nürnberg)
next prev parent reply other threads:[~2009-04-30 6:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-29 22:34 rdac priority checker changing priorities Lucas Brasilino
2009-04-30 6:25 ` Hannes Reinecke [this message]
2009-04-30 18:05 ` Chandra Seetharaman
2009-05-04 10:43 ` Hannes Reinecke
2009-05-04 17:30 ` Chandra Seetharaman
2009-06-23 0:47 ` Chandra Seetharaman
2009-06-23 6:20 ` Hannes Reinecke
2009-05-05 17:59 ` Lucas Brasilino
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=49F9443E.7040109@suse.de \
--to=hare@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox