Hi,
I've configured multipath but I'm confused with the following. When I
run "multipath -v2" I don't get any output, but if I run "multipath
-v3" I get lot's of output e.g.:
cciss!c0d0: not found in pathvec
cciss!c0d0: mask = 0x1f
dm-0: blacklisted
hda: blacklisted
loop0: blacklisted
loop1: blac
On 10/13/2009 10:17 AM, Dan Track wrote:
Hi,
I've configured multipath but I'm confused with the following. When I
run "multipath -v2" I don't get any output, but if I run "multipath
-v3" I get lot's of output e.g.:
cciss!c0d0: not found in pathvec
cciss!c0d0: mask = 0x1f
dm-0: blacklisted
hda:
On Tue, Oct 13, 2009 at 5:48 PM, Phil Meyer wrote:
> On 10/13/2009 10:17 AM, Dan Track wrote:
>>
>> Hi,
>>
>> I've configured multipath but I'm confused with the following. When I
>> run "multipath -v2" I don't get any output, but if I run "multipath
>> -v3" I get lot's of output e.g.:
>>
>> cciss
On Tue, 2009-10-13 at 10:48 -0600, Phil Meyer wrote:
> Yes, multipath -l may not show anything. multipath -v3 should always
multipath -l and multipath -ll will always produce output when there is
an active multipath device on the system (as is the case here) but
that's not what the OP was asking
On Tue, 2009-10-13 at 17:17 +0100, Dan Track wrote:
> I've configured multipath but I'm confused with the following. When I
> run "multipath -v2" I don't get any output, but if I run "multipath
> -v3" I get lot's of output e.g.:
> mpath0: pgfailback = -2 (controller setting)
> mpath0: pgpolicy =
On Tue, 2009-10-13 at 18:23 +0100, Dan Track wrote:
> I've already got the following /dev/mapper/mpath0 and
> /dev/mpath/3600c0ff000d7ba4f4575b24a0100. Can you tell me how I
> can reload the config and end up with /dev/mapper/san1?
That's a little bit strange; normally you'd expect the /dev/mp
On Tue, Oct 13, 2009 at 6:45 PM, Bryn M. Reeves wrote:
> On Tue, 2009-10-13 at 18:23 +0100, Dan Track wrote:
>> I've already got the following /dev/mapper/mpath0 and
>> /dev/mpath/3600c0ff000d7ba4f4575b24a0100. Can you tell me how I
>> can reload the config and end up with /dev/mapper/san1?
>
On Tue, Oct 13, 2009 at 7:01 PM, Dan Track wrote:
> On Tue, Oct 13, 2009 at 6:45 PM, Bryn M. Reeves wrote:
>> On Tue, 2009-10-13 at 18:23 +0100, Dan Track wrote:
>>> I've already got the following /dev/mapper/mpath0 and
>>> /dev/mpath/3600c0ff000d7ba4f4575b24a0100. Can you tell me how I
>>> c
