[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [dm-devel] RE: dm-devel Digest, Vol 18, Issue 2
- From: "Christopher C. Weis" <ccweis gmail com>
- To: device-mapper development <dm-devel redhat com>
- Subject: Re: [dm-devel] RE: dm-devel Digest, Vol 18, Issue 2
- Date: Wed, 03 Aug 2005 15:33:58 -0500
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
- References:
- [dm-devel] RE: dm-devel Digest, Vol 18, Issue 2
- Re: [dm-devel] RE: dm-devel Digest, Vol 18, Issue 2
- Re: [dm-devel] RE: dm-devel Digest, Vol 18, Issue 2
- Re: [dm-devel] RE: dm-devel Digest, Vol 18, Issue 2
- Re: [dm-devel] RE: dm-devel Digest, Vol 18, Issue 2
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]