From: Scott Dungan <scott@gps.caltech.edu>
To: dm-devel@redhat.com
Subject: Re: Manual failback commands
Date: Thu, 04 Feb 2010 10:18:43 -0800 [thread overview]
Message-ID: <4B6B0F83.7080201@gps.caltech.edu> (raw)
In-Reply-To: <4B69D495.4060702@gps.caltech.edu>
On 2/3/2010 11:55 AM, Scott Dungan wrote:
> Yes, I understand that. If I run 'multipathd -k' and then help, these
> are the commands that are listed:
>
> list|show paths
> list|show maps
> add path $path
> remove|del path $path
> add map $map
> remove|del map $map
> switch|switchgroup map $map group $group
> dump pathvec
> reconfigure
> disablequeueing map $map
> restorequeueing map $map
>
>
> Where are the 'reinstate path' or 'fail path' directives you mention
> in this thread? In case this is a version issue, we are running with
> version device-mapper-multipath-0.4.7-30.el5_4.4. What version are you
> running where the 'reinstate path' or 'fail path' directives are
> listed in help or otherwise function?
>
> -Scott
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
>
It looks like I have answered my own question. I was confused about
which version we were running. I was testing against version 4.5. Those
commands are not available in version 4.5 (RHEL 4.8). They are present
in version 4.7 (RHEL 5.x).
Thanks for your help.
-Scott
--
Scott A Dungan
Systems Administrator
GPS Division
California Institute of Technology
Phone: (626) 395-3170
Fax: (626) 585-1917
prev parent reply other threads:[~2010-02-04 18:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-03 0:39 Manual failback commands Scott Dungan
2010-02-03 1:07 ` Christophe Varoqui
2010-02-03 16:49 ` Scott Dungan
2010-02-03 16:59 ` Christophe Varoqui
2010-02-03 17:44 ` Scott Dungan
2010-02-03 19:33 ` Christophe Varoqui
2010-02-03 19:55 ` Scott Dungan
2010-02-04 18:18 ` Scott Dungan [this message]
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=4B6B0F83.7080201@gps.caltech.edu \
--to=scott@gps.caltech.edu \
--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.