From: Benjamin Marzinski <bmarzins@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: about multipath path group
Date: Mon, 3 Aug 2009 14:31:41 -0500 [thread overview]
Message-ID: <20090803193141.GQ15326@ether.msp.redhat.com> (raw)
In-Reply-To: <2005566d0907212349i13c7d5aft7af3506dc572b8e7@mail.gmail.com>
On Wed, Jul 22, 2009 at 02:49:39PM +0800, 杨伟 wrote:
> Dear all:
>
> Q1: In RHEL 5.2, make and make install multipath-tools-0.4.8, why does not
> command "multipath -p" work well?
Are you using the upstream or the RHEL code. multipath -p does work in
the RHEL code, although, if you run multipath again, or reconfigure
multipathd, it will notice that your devices aren't set up the way the
config says they should be, and it will change them back. In general,
multipath -p is pretty worthless, you should change the configuration to
use the path grouping policy you want.
>
> Q2: In RHEL 5.2, configure path group policy as failover or group_by_prio,
> and then create path-prio.sh to set the priority of paths. however, the
> path group with the highest priority is not always active, if I don't
> recreate the multipath devices. why is that? how I make the path group
> with the highest priority is active on-line?
By default, multipath is configured for manual failback. This means
that multipathd won't switch from the current active pathgroup to a
higher priority one, unless you manually force it to do so. The
easiest way to do this is by running
# service multipathd reload or
# multipathd -k"reconfigure"
adding
defaults {
<other_defaults>
failback immediate
}
to /etc/multipath.conf will make multipath immdiately switch to the
highest priority path group.
-Ben
>
> William
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
next prev parent reply other threads:[~2009-08-03 19:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-22 6:49 about multipath path group 杨伟
2009-08-03 19:31 ` Benjamin Marzinski [this message]
2009-08-04 10:08 ` 杨伟
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=20090803193141.GQ15326@ether.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.