Multipath command output - Help with understanding output
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: blacklisted loop2: blacklisted loop3: blacklisted loop4: blacklisted loop5: blacklisted loop6: blacklisted loop7: blacklisted md0: blacklisted ram0: blacklisted ram10: blacklisted ram11: blacklisted ram12: blacklisted ram13: blacklisted ram14: blacklisted ram15: blacklisted ram1: blacklisted ram2: blacklisted ram3: blacklisted ram4: blacklisted ram5: blacklisted ram6: blacklisted ram7: blacklisted ram8: blacklisted ram9: blacklisted sda: not found in pathvec sda: mask = 0x1f sda: bus = 1 sda: dev_t = 8:0 sda: size = 19534921728 sda: vendor = HP sda: product = MSA2012sa sda: rev = J300 sda: h:b:t:l = 0:0:0:1 sda: serial = 00c0ffd7ba4f4575b24a0100 sda: path checker = tur (controller setting) sda: state = 2 sda: getprio = /sbin/mpath_prio_alua %d (controller setting) sda: prio = 50 sda: getuid = /sbin/hp_scsi_id -g -u -n -s /block/%n (controller setting) sda: uid = 3600c0ff000d7ba4f4575b24a0100 (callout) sdb: not found in pathvec sdb: mask = 0x1f sdb: bus = 1 sdb: dev_t = 8:16 sdb: size = 19534921728 sdb: vendor = HP sdb: product = MSA2012sa sdb: rev = J300 sdb: h:b:t:l = 1:0:0:2 sdb: serial = 00c0ffd7ba4f4575b24a0100 sdb: path checker = tur (controller setting) sdb: state = 2 sdb: getprio = /sbin/mpath_prio_alua %d (controller setting) sdb: prio = 10 sdb: getuid = /sbin/hp_scsi_id -g -u -n -s /block/%n (controller setting) sdb: uid = 3600c0ff000d7ba4f4575b24a0100 (callout) = paths list = uuid hcildev dev_t pri dm_st chk_st vend/pr 3600c0ff000d7ba4f4575b24a0100 0:0:0:1 sda 8:0 50 [undef][ready] HP,MSA2 3600c0ff000d7ba4f4575b24a0100 1:0:0:2 sdb 8:16 10 [undef][ready] HP,MSA2 params = 1 queue_if_no_path 0 2 1 round-robin 0 1 1 8:0 100 round-robin 0 1 1 8:16 100 status = 2 0 0 0 2 1 A 0 1 0 8:0 A 0 E 0 1 0 8:16 A 0 Found matching wwid [3600c0ff000d7ba4f4575b24a0100] in bindings file. Setting alias to mpath0 sda: ownership set to mpath0 sda: not found in pathvec sda: mask = 0xc sda: state = 2 sda: prio = 50 sdb: ownership set to mpath0 sdb: not found in pathvec sdb: mask = 0xc sdb: state = 2 sdb: prio = 10 mpath0: pgfailback = -2 (controller setting) mpath0: pgpolicy = group_by_prio (controller setting) mpath0: selector = round-robin 0 (controller setting) mpath0: features = 0 (internal default) mpath0: hwhandler = 0 (controller setting) mpath0: rr_weight = 1 (internal default) mpath0: minio = 100 (controller setting) mpath0: no_path_retry = 18 (controller setting) pg_timeout = NONE (internal default) mpath0: set ACT_NOTHING (map unchanged) multipath -ll mpath0 (3600c0ff000d7ba4f4575b24a0100) dm-0 HP,MSA2012sa [size=9.1T][features=1 queue_if_no_path][hwhandler=0][rw] \_ round-robin 0 [prio=50][active] \_ 0:0:0:1 sda 8:0 [active][ready] \_ round-robin 0 [prio=10][enabled] \_ 1:0:0:2 sdb 8:16 [active][ready] Does that mean multipath is working on /dev/sda and /dev/sdb? Is the lack of output for multipath -v2 a concern? Thanks Dan -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Multipath command output - Help with understanding output
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: blacklisted
loop0: blacklisted
loop1: blacklisted
loop2: blacklisted
loop3: blacklisted
loop4: blacklisted
loop5: blacklisted
loop6: blacklisted
loop7: blacklisted
md0: blacklisted
ram0: blacklisted
ram10: blacklisted
ram11: blacklisted
ram12: blacklisted
ram13: blacklisted
ram14: blacklisted
ram15: blacklisted
ram1: blacklisted
ram2: blacklisted
ram3: blacklisted
ram4: blacklisted
ram5: blacklisted
ram6: blacklisted
ram7: blacklisted
ram8: blacklisted
ram9: blacklisted
sda: not found in pathvec
sda: mask = 0x1f
sda: bus = 1
sda: dev_t = 8:0
sda: size = 19534921728
sda: vendor = HP
sda: product = MSA2012sa
sda: rev = J300
sda: h:b:t:l = 0:0:0:1
sda: serial = 00c0ffd7ba4f4575b24a0100
sda: path checker = tur (controller setting)
sda: state = 2
sda: getprio = /sbin/mpath_prio_alua %d (controller setting)
sda: prio = 50
sda: getuid = /sbin/hp_scsi_id -g -u -n -s /block/%n (controller setting)
sda: uid = 3600c0ff000d7ba4f4575b24a0100 (callout)
sdb: not found in pathvec
sdb: mask = 0x1f
sdb: bus = 1
sdb: dev_t = 8:16
sdb: size = 19534921728
sdb: vendor = HP
sdb: product = MSA2012sa
sdb: rev = J300
sdb: h:b:t:l = 1:0:0:2
sdb: serial = 00c0ffd7ba4f4575b24a0100
sdb: path checker = tur (controller setting)
sdb: state = 2
sdb: getprio = /sbin/mpath_prio_alua %d (controller setting)
sdb: prio = 10
sdb: getuid = /sbin/hp_scsi_id -g -u -n -s /block/%n (controller setting)
sdb: uid = 3600c0ff000d7ba4f4575b24a0100 (callout)
= paths list =
uuid hcildev dev_t pri dm_st chk_st vend/pr
3600c0ff000d7ba4f4575b24a0100 0:0:0:1 sda 8:0 50 [undef][ready] HP,MSA2
3600c0ff000d7ba4f4575b24a0100 1:0:0:2 sdb 8:16 10 [undef][ready] HP,MSA2
params = 1 queue_if_no_path 0 2 1 round-robin 0 1 1 8:0 100
round-robin 0 1 1 8:16 100
status = 2 0 0 0 2 1 A 0 1 0 8:0 A 0 E 0 1 0 8:16 A 0
Found matching wwid [3600c0ff000d7ba4f4575b24a0100] in bindings file.
Setting alias to mpath0
sda: ownership set to mpath0
sda: not found in pathvec
sda: mask = 0xc
sda: state = 2
sda: prio = 50
sdb: ownership set to mpath0
sdb: not found in pathvec
sdb: mask = 0xc
sdb: state = 2
sdb: prio = 10
mpath0: pgfailback = -2 (controller setting)
mpath0: pgpolicy = group_by_prio (controller setting)
mpath0: selector = round-robin 0 (controller setting)
mpath0: features = 0 (internal default)
mpath0: hwhandler = 0 (controller setting)
mpath0: rr_weight = 1 (internal default)
mpath0: minio = 100 (controller setting)
mpath0: no_path_retry = 18 (controller setting)
pg_timeout = NONE (internal default)
mpath0: set ACT_NOTHING (map unchanged)
multipath -ll
mpath0 (3600c0ff000d7ba4f4575b24a0100) dm-0 HP,MSA2012sa
[size=9.1T][features=1 queue_if_no_path][hwhandler=0][rw]
\_ round-robin 0 [prio=50][active]
\_ 0:0:0:1 sda 8:0 [active][ready]
\_ round-robin 0 [prio=10][enabled]
\_ 1:0:0:2 sdb 8:16 [active][ready]
Does that mean multipath is working on /dev/sda and /dev/sdb? Is the
lack of output for multipath -v2 a concern?
Thanks
Dan
Yes, multipath -l may not show anything. multipath -v3 should always
show similar to the output above, and what you see is that it found two
paths to the same device, which is good. It is also going to round
robin reads and writes, which is also good.
You may want to customize things a bit to make it easier to remember, or
in case you add another unit or device.
I would suggest adding at least these to /etc/multipath.conf:
multipaths {
multipath {
uuid 3600c0ff000d7ba4f4575b24a0100
failbackimmediate
rr_min_io1000
aliassan1
}
devices {
device {
vendorHP
productMSA2
features1 queue_if_no_path
path_checkertur
}
}
This creats the device: /dev/mapper/san1 which can then be partitioned
and mkfs.
Good Luck!
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Multipath command output - Help with understanding output
On Tue, Oct 13, 2009 at 5:48 PM, Phil Meyer pme...@themeyerfarm.com 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!c0d0: not found in pathvec
cciss!c0d0: mask = 0x1f
dm-0: blacklisted
hda: blacklisted
loop0: blacklisted
loop1: blacklisted
loop2: blacklisted
loop3: blacklisted
loop4: blacklisted
loop5: blacklisted
loop6: blacklisted
loop7: blacklisted
md0: blacklisted
ram0: blacklisted
ram10: blacklisted
ram11: blacklisted
ram12: blacklisted
ram13: blacklisted
ram14: blacklisted
ram15: blacklisted
ram1: blacklisted
ram2: blacklisted
ram3: blacklisted
ram4: blacklisted
ram5: blacklisted
ram6: blacklisted
ram7: blacklisted
ram8: blacklisted
ram9: blacklisted
sda: not found in pathvec
sda: mask = 0x1f
sda: bus = 1
sda: dev_t = 8:0
sda: size = 19534921728
sda: vendor = HP
sda: product = MSA2012sa
sda: rev = J300
sda: h:b:t:l = 0:0:0:1
sda: serial = 00c0ffd7ba4f4575b24a0100
sda: path checker = tur (controller setting)
sda: state = 2
sda: getprio = /sbin/mpath_prio_alua %d (controller setting)
sda: prio = 50
sda: getuid = /sbin/hp_scsi_id -g -u -n -s /block/%n (controller setting)
sda: uid = 3600c0ff000d7ba4f4575b24a0100 (callout)
sdb: not found in pathvec
sdb: mask = 0x1f
sdb: bus = 1
sdb: dev_t = 8:16
sdb: size = 19534921728
sdb: vendor = HP
sdb: product = MSA2012sa
sdb: rev = J300
sdb: h:b:t:l = 1:0:0:2
sdb: serial = 00c0ffd7ba4f4575b24a0100
sdb: path checker = tur (controller setting)
sdb: state = 2
sdb: getprio = /sbin/mpath_prio_alua %d (controller setting)
sdb: prio = 10
sdb: getuid = /sbin/hp_scsi_id -g -u -n -s /block/%n (controller setting)
sdb: uid = 3600c0ff000d7ba4f4575b24a0100 (callout)
= paths list =
uuid hcil dev dev_t pri dm_st chk_st
vend/pr
3600c0ff000d7ba4f4575b24a0100 0:0:0:1 sda 8:0 50 [undef][ready]
HP,MSA2
3600c0ff000d7ba4f4575b24a0100 1:0:0:2 sdb 8:16 10 [undef][ready]
HP,MSA2
params = 1 queue_if_no_path 0 2 1 round-robin 0 1 1 8:0 100
round-robin 0 1 1 8:16 100
status = 2 0 0 0 2 1 A 0 1 0 8:0 A 0 E 0 1 0 8:16 A 0
Found matching wwid [3600c0ff000d7ba4f4575b24a0100] in bindings file.
Setting alias to mpath0
sda: ownership set to mpath0
sda: not found in pathvec
sda: mask = 0xc
sda: state = 2
sda: prio = 50
sdb: ownership set to mpath0
sdb: not found in pathvec
sdb: mask = 0xc
sdb: state = 2
sdb: prio = 10
mpath0: pgfailback = -2 (controller setting)
mpath0: pgpolicy = group_by_prio (controller setting)
mpath0: selector = round-robin 0 (controller setting)
mpath0: features = 0 (internal default)
mpath0: hwhandler = 0 (controller setting)
mpath0: rr_weight = 1 (internal default)
mpath0: minio = 100 (controller setting)
mpath0: no_path_retry = 18 (controller setting)
pg_timeout = NONE (internal default)
mpath0: set ACT_NOTHING (map unchanged)
multipath -ll
mpath0 (3600c0ff000d7ba4f4575b24a0100) dm-0 HP,MSA2012sa
[size=9.1T][features=1 queue_if_no_path][hwhandler=0][rw]
\_ round-robin 0 [prio=50][active]
\_ 0:0:0:1 sda 8:0 [active][ready]
\_ round-robin 0 [prio=10][enabled]
\_ 1:0:0:2 sdb 8:16 [active][ready]
Does that mean multipath is working on /dev/sda and /dev/sdb? Is the
lack of output for multipath -v2 a concern?
Thanks
Dan
Yes, multipath -l may not show anything. multipath -v3 should always show
similar to the output above, and what you see is that it found two paths to
the same device, which is good. It is also going to round robin reads and
writes, which is also good.
You may want to customize things a bit to make it easier to remember, or in
case you add another unit or device.
I would suggest adding at least these to /etc/multipath.conf:
multipaths {
multipath {
uuid 3600c0ff000d7ba4f4575b24a0100
failback immediate
rr_min_io 1000
alias san1
}
devices {
device {
vendor HP
product MSA2
features 1 queue_if_no_path
path_checker tur
}
}
This creats the device: /dev/mapper/san1 which can then be partitioned and
mkfs.
Good Luck!
Brilliant, many thanks for that.
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?
Also when running pvcreate should I run
pvcreate /dev/mapper/mpath0
or
pvcreate /dev/mpath/3600c0ff000d7ba4f4575b24a0100
?
Thanks again.
Dan
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Multipath command output - Help with understanding output
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 about.
show similar to the output above, and what you see is that it found two
paths to the same device, which is good. It is also going to round
robin reads and writes, which is also good.
That's not correct - the output shows two path groups and the device is
using group_by_prio path grouping policy:
mpath0: pgpolicy = group_by_prio (controller setting)
[...]
multipath -ll
mpath0 (3600c0ff000d7ba4f4575b24a0100) dm-0 HP,MSA2012sa
[size=9.1T][features=1 queue_if_no_path][hwhandler=0][rw]
\_ round-robin 0 [prio=50][active]
\_ 0:0:0:1 sda 8:0 [active][ready]
\_ round-robin 0 [prio=10][enabled]
\_ 1:0:0:2 sdb 8:16 [active][ready]
So the I/O will only flow over one of these path groups until there is a
failure and we switch to the other path group. I think the newer MSAs
(which this is) do support ALUA which would allow you to distribute the
I/O with some penalty on the non-preferred paths but the default
multipath configuration for this model of MSA will not do this.
You may want to customize things a bit to make it easier to remember, or
in case you add another unit or device.
I would suggest adding at least these to /etc/multipath.conf:
multipaths {
multipath {
uuid 3600c0ff000d7ba4f4575b24a0100
failbackimmediate
rr_min_io1000
aliassan1
}
The OP was already using the user_friendly_names feature. Although
adding explicit aliases is useful in some situations many users prefer
to just use the automatically assigned mpathN names.
devices {
device {
vendorHP
productMSA2
features1 queue_if_no_path
path_checkertur
}
}
Why would you override the compiled-in settings for this storage
controller with this? There are two different generations of MSA2*
firmware out there which need different handling - the compiled in
defaults are careful to select the appropriate settings by matching
against the exact product string (MSA2[02]12fc|MSA2012i vs.
MSA2012sa|MSA23(12|24)(fc|i|sa)).
Regards,
Bryn.
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Multipath command output - Help with understanding output
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.: snip mpath0: pgfailback = -2 (controller setting) mpath0: pgpolicy = group_by_prio (controller setting) mpath0: selector = round-robin 0 (controller setting) mpath0: features = 0 (internal default) mpath0: hwhandler = 0 (controller setting) mpath0: rr_weight = 1 (internal default) mpath0: minio = 100 (controller setting) mpath0: no_path_retry = 18 (controller setting) pg_timeout = NONE (internal default) mpath0: set ACT_NOTHING (map unchanged) ^^ here's why you're seeing no output from multipath -v2. At this verbosity level the command only prints output when it changes something. Since your mpath0 device was already up and running at this point there's no changes to make and -v2 will be silent. If there's nothing using the device then you can try running multipath -F to flush all multipath devices then re-running multipath -v2 - this should re-create the map and print something to the terminal indicating what it's done. multipath -ll mpath0 (3600c0ff000d7ba4f4575b24a0100) dm-0 HP,MSA2012sa [size=9.1T][features=1 queue_if_no_path][hwhandler=0][rw] \_ round-robin 0 [prio=50][active] \_ 0:0:0:1 sda 8:0 [active][ready] \_ round-robin 0 [prio=10][enabled] \_ 1:0:0:2 sdb 8:16 [active][ready] Does that mean multipath is working on /dev/sda and /dev/sdb? Is the Yes. lack of output for multipath -v2 a concern? No. Cheers, Bryn. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Multipath command output - Help with understanding output
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/mpath entries to follow the same naming as is used in /dev/mapper. That said, the symlinks in /dev/mpath are nothing but trouble and it is strongly advised that you don't use them for anything. The main problem is that they can at times get out-of-sync with the device-mapper status. This can lead to a range of problems such as failed booting (since the correct device names don't exist at the point they should in the boot process) to data corruption when a stale symlink ends up pointing to the wrong multipath device. This happens because the device nodes in /dev/mapper are managed by libdevmapper and so are updated in-sync with the state of the devices in the kernel but the symlinks are managed in userspace by udev and so there can be delays between the device-mapper's state changing and the corresponding symlinks getting updated. Also when running pvcreate should I run pvcreate /dev/mapper/mpath0 Always prefer the names in /dev/mapper when working with multipath devices. Regards, Bryn. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Multipath command output - Help with understanding output
On Tue, Oct 13, 2009 at 6:45 PM, Bryn M. Reeves b...@redhat.com 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? That's a little bit strange; normally you'd expect the /dev/mpath entries to follow the same naming as is used in /dev/mapper. That said, the symlinks in /dev/mpath are nothing but trouble and it is strongly advised that you don't use them for anything. The main problem is that they can at times get out-of-sync with the device-mapper status. This can lead to a range of problems such as failed booting (since the correct device names don't exist at the point they should in the boot process) to data corruption when a stale symlink ends up pointing to the wrong multipath device. This happens because the device nodes in /dev/mapper are managed by libdevmapper and so are updated in-sync with the state of the devices in the kernel but the symlinks are managed in userspace by udev and so there can be delays between the device-mapper's state changing and the corresponding symlinks getting updated. Also when running pvcreate should I run pvcreate /dev/mapper/mpath0 Always prefer the names in /dev/mapper when working with multipath devices. Regards, Bryn. Many many thanks Bryn. I owe you one. Thanks Dan -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Multipath command output - Help with understanding output
On Tue, Oct 13, 2009 at 7:01 PM, Dan Track dan.tr...@gmail.com wrote: On Tue, Oct 13, 2009 at 6:45 PM, Bryn M. Reeves b...@redhat.com 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? That's a little bit strange; normally you'd expect the /dev/mpath entries to follow the same naming as is used in /dev/mapper. That said, the symlinks in /dev/mpath are nothing but trouble and it is strongly advised that you don't use them for anything. The main problem is that they can at times get out-of-sync with the device-mapper status. This can lead to a range of problems such as failed booting (since the correct device names don't exist at the point they should in the boot process) to data corruption when a stale symlink ends up pointing to the wrong multipath device. This happens because the device nodes in /dev/mapper are managed by libdevmapper and so are updated in-sync with the state of the devices in the kernel but the symlinks are managed in userspace by udev and so there can be delays between the device-mapper's state changing and the corresponding symlinks getting updated. Also when running pvcreate should I run pvcreate /dev/mapper/mpath0 Always prefer the names in /dev/mapper when working with multipath devices. Regards, Bryn. Many many thanks Bryn. I owe you one. Thanks Dan Bryn, Is there any chance you could help with the my other mail I sent titled: Testing Device Failure. I basically want to test this setup. Thanks Dan -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
