From: "Christopher C. Weis" <ccweis@gmail.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: RE: dm-devel Digest, Vol 18, Issue 2
Date: Wed, 03 Aug 2005 15:33:58 -0500 [thread overview]
Message-ID: <42F12A36.1090205@gmail.com> (raw)
In-Reply-To: <1123095225.21778.45.camel@zezette>
christophe varoqui wrote:
>>
>>
>>
>> Does this mean that "group_by_serial" utilizes a
>> "default_prio_callout" program/script as well, or is there
>> another callout (or something totally different that I'm
>> missing)?
>>
>>I've verified that by writing my own "default_prio_callout" script I
>>can achieve what I want with both the "group_by_priority" and
>>"failover" policies. Once I get done testing/tweaking the script,
>>I'll post it in case anyone else wants it.
>>
>>I can't seem to make group_by_serial work, although I'm not sure I
>>understand this policy very well. It sounds like it's supposed to
>>make all paths that go to a particular controller (serial?) be in the
>>same priority group. For me, it's no different than multibus.
>>Probably my misunderstanding, so I'm open to any suggestions...
>>
>>
>>
>"/sbin/multipath -v4" will verbosely show you the path discovery phase,
>including the discovered serials.
>
>May be you'll understand better what happens with your hardware.
>
>Regards,
>
>
Ahhh, that makes things much clearer. Thanks a bunch everyone.
~Chris
next prev parent reply other threads:[~2005-08-03 20:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-02 19:07 dm-devel Digest, Vol 18, Issue 2 goggin, edward
2005-08-02 20:27 ` christophe varoqui
2005-08-02 21:49 ` Christopher Weis
2005-08-03 3:01 ` Christopher Weis
2005-08-03 18:53 ` christophe varoqui
2005-08-03 20:33 ` Christopher C. Weis [this message]
2005-08-03 18:50 ` christophe varoqui
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=42F12A36.1090205@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.