McCulloch, Alan
2009-Sep-17 00:31 UTC
[CentOS] multipath using defaults rather than multipath.conf contents for some devices (?) - why ?
hi all
We have a rh linux server connected to two HP SAN controllers, one an HSV200 (on
the way out),
the other an HSV400 (on the way in). (Via a Qlogic HBA).
/etc/multipath.conf contains this :
device
{
vendor "(COMPAQ|HP)"
product "HSV1[01]1|HSV2[01]0|HSV300|HSV4[05]0"
getuid_callout "/sbin/scsi_id -g -u -s /block/%n"
prio_callout "/sbin/mpath_prio_alua /dev/%n"
hardware_handler "0"
path_selector "round-robin 0"
path_grouping_policy group_by_prio
failback immediate
rr_weight uniform
no_path_retry 18
rr_min_io 100
path_checker tur
}
- but our actual multipathing as shown by multipath -ll , and multipath -ll -v 3
looks as though for the
HSV400 it is using the defaults rather than these settings. The defaults are
#defaults {
# udev_dir /dev
# polling_interval 10
# selector "round-robin 0"
# path_grouping_policy multibus
# getuid_callout "/sbin/scsi_id -g -u -s /block/%n"
# prio_callout /bin/true
# path_checker readsector0
# rr_min_io 100
# rr_weight priorities
# failback immediate
# no_path_retry fail
# user_friendly_name yes
and multipath -ll reports :
.
.
[snip other HSV400 paths - all similar]
mpath12 (3600508b40007518f0000900000520000) dm-1 HP,HSV400
[size=150G][features=0][hwhandler=0]
\_ round-robin 0 [prio=1][active]
\_ 0:0:5:9 sdab 65:176 [active][ready]
\_ round-robin 0 [prio=1][enabled]
\_ 0:0:3:9 sdn 8:208 [active][ready]
\_ round-robin 0 [prio=1][enabled]
\_ 0:0:4:9 sdu 65:64 [active][ready]
mpath11 (3600508b40007518f0000700000370000) dm-6 HP,HSV200
[size=200G][features=1 queue_if_no_path][hwhandler=0]
\_ round-robin 0 [prio=50][active]
\_ 0:0:1:7 sdd 8:48 [active][ready]
\_ round-robin 0 [prio=10][enabled]
\_ 0:0:2:7 sdh 8:112 [active][ready]
.
.
[snip other HSV200 paths - all similar]
multipath -ll -v 3 includes explicit statements that defaults are being used for
the HSV400
(long output snipped...)
sdaa: path checker = readsector0 (config file default)
versus
sda: path checker = tur (controller setting)
sdx: getprio = NULL (internal default)
versus
sdd: getprio = /sbin/mpath_prio_alua %n (controller setting)
- furthermore we see in the log file messages from both readsector0 *and* tur
rather than just tur if the correct settings were used , which also backs that
up.
My questions are basically - why is it happening , and how to fix it ?
The vendor and product regexps definitely do match both "HSP" and both
"HSV200" and "HSV400" respectively
so it doesn't seem that fiddling with the patterns will work , and I'm
sure this config has been tested.
Its not due to this server having to deal with two controllers - we have a
second server that only mounts from
the HSV400, and its multipath settings appear to be entirely the defaults, and
not what we have set.
(And conversely, its not due to the conf file not being read at all - since the
server with two controllers
is using the correct config for one of them , but not the other.)
thanks for any tips and I will summarise.
Cheers
AMcC
======================================================================Attention:
The information contained in this message and/or attachments
from AgResearch Limited is intended only for the persons or entities
to which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipients is prohibited by AgResearch
Limited. If you have received this message in error, please notify the
sender immediately.
======================================================================--------------
next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.centos.org/pipermail/centos/attachments/20090917/cca2f04f/attachment.html>
nate
2009-Sep-17 01:07 UTC
[CentOS] multipath using defaults rather than multipath.conf contents for some devices (?) - why ?
McCulloch, Alan wrote:> hi all > > We have a rh linux server connected to two HP SAN controllers, one an HSV200 > (on the way out), > the other an HSV400 (on the way in). (Via a Qlogic HBA). > > /etc/multipath.conf contains this : > > device > { > vendor "(COMPAQ|HP)" > product "HSV1[01]1|HSV2[01]0|HSV300|HSV4[05]0"What does /proc/scsi/scsi say? Perhaps your config doesn't match what the system is being presented. For my MPIO my vendor suggested setting the defaults manually in the config file so my config file is: defaults { udev_dir /dev polling_interval 10 default_selector "round-robin 0" default_path_grouping_policy multibus default_getuid_callout "/sbin/scsi_id -g -u -s /block/%n" default_prio_callout /bin/true rr_wmin_io 100 rr_weight priorities failback immediate } blacklist { wwid 26353900f02796769 devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*" devnode "^hd[a-z][0-9]*" devnode "^cciss*" } devices { device { vendor "3PARdata" product "VV " path_grouping_policy multibus path_checker tur no_path_retry 60 } } multipath -l 350002ac0006a0714dm-1 3PARdata,VV [size=1.0T][features=0][hwhandler=0] \_ round-robin 0 [prio=0][active] \_ 1:0:0:3 sdc 8:32 [active][undef] \_ 1:0:1:3 sde 8:64 [active][undef] \_ 2:0:0:3 sdg 8:96 [active][undef] \_ 2:0:1:3 sdi 8:128 [active][undef] 350002ac000790714dm-0 3PARdata,VV [size=2.0T][features=0][hwhandler=0] \_ round-robin 0 [prio=0][active] \_ 1:0:0:2 sdb 8:16 [active][undef] \_ 1:0:1:2 sdd 8:48 [active][undef] \_ 2:0:0:2 sdf 8:80 [active][undef] \_ 2:0:1:2 sdh 8:112 [active][undef] /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 32 Lun: 00 Vendor: DP Model: BACKPLANE Rev: 1.05 Type: Enclosure ANSI SCSI revision: 05 Host: scsi0 Channel: 02 Id: 00 Lun: 00 Vendor: DELL Model: PERC 6/i Rev: 1.11 Type: Direct-Access ANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 02 Vendor: 3PARdata Model: VV Rev: 0000 Type: Direct-Access ANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 03 Vendor: 3PARdata Model: VV Rev: 0000 Type: Direct-Access ANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 01 Lun: 02 Vendor: 3PARdata Model: VV Rev: 0000 Type: Direct-Access ANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 01 Lun: 03 Vendor: 3PARdata Model: VV Rev: 0000 Type: Direct-Access ANSI SCSI revision: 05 Host: scsi2 Channel: 00 Id: 00 Lun: 02 Vendor: 3PARdata Model: VV Rev: 0000 Type: Direct-Access ANSI SCSI revision: 05 Host: scsi2 Channel: 00 Id: 00 Lun: 03 Vendor: 3PARdata Model: VV Rev: 0000 Type: Direct-Access ANSI SCSI revision: 05 Host: scsi2 Channel: 00 Id: 01 Lun: 02 Vendor: 3PARdata Model: VV Rev: 0000 Type: Direct-Access ANSI SCSI revision: 05 Host: scsi2 Channel: 00 Id: 01 Lun: 03 Vendor: 3PARdata Model: VV Rev: 0000 Type: Direct-Access ANSI SCSI revision: 05 nate