From: "Christopher C. Weis" <ccweis@gmail.com>
To: dm-devel@redhat.com
Subject: multipath configuration questions
Date: Tue, 02 Aug 2005 09:37:14 -0500 [thread overview]
Message-ID: <42EF851A.20108@gmail.com> (raw)
Hello. I don't know if this is the proper place to post this, so please
point me to the correct list if it isn't.
I have a multipath SAN environment with storage controllers that are
active/active. However, the controllers are not active/active at the
LUN-level without a performance penalty, meaning if two servers want to
see the same LUN (as in a clustered filesystem environment), they both
need to be using the same controller. I'm trying to figure out a way to
statically "order" the paths so that I can copy a config to all of the
nodes using the CFS.
From what I've read, in a single-server environment with controllers
such as the ones I'm dealing with, the path_grouping_policy should be
set to "group_by_serial", which should work fine, but in a clustered
environment, I need to be sure that the path ordering is the same.
Are there any path_selectors, other than round-robin, that might
accomplish this? Any other ideas?
Thanks. I appreciate any information that can be offered.
~Chris
reply other threads:[~2005-08-02 14:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=42EF851A.20108@gmail.com \
--to=ccweis@gmail.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.