From: Tore Anderson <tore@linpro.no>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: path priorities on Sun's 6140
Date: Tue, 18 Sep 2007 09:39:38 +0200 [thread overview]
Message-ID: <46EF80BA.1020605@linpro.no> (raw)
In-Reply-To: <66F461DD7EDEEF4AA928FCC80B425B520468B9@c2kp01mail.cucbc.com>
* James Fillman
> Ok. So I just realized that if I want to try the new RDAC support,
> then I have to install the new beta kernel as well. It includes the
> RDAC hardware handler.
>
> I'm under serious pressure to get my cluster up and running asap and
> I don't think I want to be installing a bunch of beta packages onto
> my production servers. Especially kernels.
To me the benefit of RDAC mode would far outweigh the disadvantage of
knowing you're running a beta kernel, but that's your call...
With AVT mode you will have I/O interruptions and volume failovers when
a node in your cluster boots. It's unavoidable. You'll probably want
to test really well how the rest of the cluster behaves in such situations.
> So this might mean not exploring the RDAC solution. Redhat's docs say
> that they support a Sun OpenStorage D280 and our Sun rep says the
> 6140 is essentially identical. If that's the case, what am I don't
> wrong?
The original hardware is called Engenio 3994 - you might be able to
confirm that the D280 is the same by Googling some. (The IBM DS4700
model 72 is also the same, by the way). RH probably supports it in AVT
mode. Your configuration looks okay to me, different
path_grouping_policy then what I use but as long as the prio_callout
works correctly the end result should be the same. My config looks like
this on a RHEL4 box running in AVT mode:
device {
vendor SUN.*
product CSM200_R.*
path_grouping_policy group_by_serial
path_checker tur
prio_callout "/usr/local/sbin/mpath_prio_tpc /dev/%n"
failback immediate
no_path_retry queue
}
This gives me output from 'multipath -ll' like this in a dual fabric
topology:
nfs_ny (3600a0b80002625ae0000080745dbe5ca)
[size=100 GB][features="1 queue_if_no_path"][hwhandler="0"]
\_ round-robin 0 [prio=2][enabled]
\_ 1:0:0:1 sdc 8:32 [active][ready]
\_ 2:0:1:1 sdi 8:128 [active][ready]
\_ round-robin 0 [prio=12][active]
\_ 1:0:1:1 sde 8:64 [active][ready]
\_ 2:0:0:1 sdg 8:96 [active][ready]
SCSI targets 1:0:0 and 2:0:1 are to controller A, 1:0:1 and 2:0:0 are to
controller B (the preferred one for LUN 1). I can verify that the
prio_callout works correctly by testing one path:
$ /usr/local/sbin/mpath_prio_tpc /dev/sde
6
Did you try host type AIX_FO, by the way? That was the one I found to
work the best with AVT mode.
Regards
--
Tore Anderson
next prev parent reply other threads:[~2007-09-18 7:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-14 22:02 path priorities on Sun's 6140 James Fillman
2007-09-15 6:26 ` Eckebrecht von Pappenheim
2007-09-15 9:08 ` Tore Anderson
2007-09-17 18:17 ` James Fillman
2007-09-17 18:36 ` James Fillman
2007-09-18 7:39 ` Tore Anderson [this message]
2007-09-21 22:55 ` James Fillman
2007-09-24 6:47 ` Tore Anderson
2007-09-24 16:56 ` James Fillman
2007-09-18 14:02 ` Hannes Reinecke
2007-09-17 6:21 ` Hannes Reinecke
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=46EF80BA.1020605@linpro.no \
--to=tore@linpro.no \
--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.