blacklisted paths?

blacklisted paths?

[Ray Stell]

I'm not able to get all "available" paths, 13 out of the 16 this time.  Sometimes
14 come up.   Why might these get blacklisted?  Thanks.

boot msgs:
----------
Sep 19 16:44:32 pecan kernel: qla2300 0000:01:07.0: scsi(0:0:0:0): Enabled tagged queuing, queue depth 32.
Sep 19 16:44:32 pecan kernel: qla2300 0000:01:07.0: scsi(0:0:0:1): Enabled tagged queuing, queue depth 32.
Sep 19 16:44:32 pecan kernel: qla2300 0000:01:07.0: scsi(0:0:0:2): Enabled tagged queuing, queue depth 32.
Sep 19 16:44:32 pecan kernel: qla2300 0000:01:07.0: scsi(0:0:0:3): Enabled tagged queuing, queue depth 32.
Sep 19 16:44:32 pecan kernel: qla2300 0000:01:07.0: scsi(0:0:1:0): Enabled tagged queuing, queue depth 32.
Sep 19 16:44:32 pecan kernel: qla2300 0000:01:07.0: scsi(0:0:1:1): Enabled tagged queuing, queue depth 32.
Sep 19 16:44:32 pecan kernel: qla2300 0000:01:07.0: scsi(0:0:1:2): Enabled tagged queuing, queue depth 32.
Sep 19 16:44:32 pecan kernel: qla2300 0000:01:07.0: scsi(0:0:1:3): Enabled tagged queuing, queue depth 32.
Sep 19 16:44:32 pecan kernel: qla2300 0000:01:0a.0: scsi(1:0:0:0): Enabled tagged queuing, queue depth 32.
Sep 19 16:44:32 pecan kernel: qla2300 0000:01:0a.0: scsi(1:0:0:1): Enabled tagged queuing, queue depth 32.
Sep 19 16:44:33 pecan kernel: qla2300 0000:01:0a.0: scsi(1:0:0:2): Enabled tagged queuing, queue depth 32.
Sep 19 16:44:34 pecan kernel: qla2300 0000:01:0a.0: scsi(1:0:0:3): Enabled tagged queuing, queue depth 32.
Sep 19 16:44:35 pecan kernel: qla2300 0000:01:0a.0: scsi(1:0:1:0): Enabled tagged queuing, queue depth 32.
Sep 19 16:44:35 pecan kernel: qla2300 0000:01:0a.0: scsi(1:0:1:1): Enabled tagged queuing, queue depth 32.
Sep 19 16:44:35 pecan kernel: qla2300 0000:01:0a.0: scsi(1:0:1:2): Enabled tagged queuing, queue depth 32.
Sep 19 16:44:35 pecan kernel: qla2300 0000:01:0a.0: scsi(1:0:1:3): Enabled tagged queuing, queue depth 32.

devmaps:
--------
[root@pecan ~]# multipath -ll
1IBM_____2105____________30A22206
[size=19 GB][features="0"][hwhandler="0"]
\_ round-robin 0 [active]
  \_ 0:0:0:1 sdb  8:16    [ready ][active]
  \_ 1:0:0:1 sdj  8:144   [ready ][active]
  \_ 1:0:1:1 sdn  8:208   [ready ][active]

1IBM_____2105____________50A22206
[size=19 GB][features="0"][hwhandler="0"]
\_ round-robin 0 [active]
  \_ 0:0:0:0 sda  8:0     [ready ][active]
  \_ 0:0:1:0 sde  8:64    [ready ][active]
  \_ 1:0:0:0 sdi  8:128   [ready ][active]

1IBM_____2105____________72622206
[size=19 GB][features="0"][hwhandler="0"]
\_ round-robin 0 [active]
  \_ 0:0:0:2 sdc  8:32    [ready ][active]
  \_ 0:0:1:2 sdg  8:96    [ready ][active]
  \_ 1:0:0:2 sdk  8:160   [ready ][active]
  \_ 1:0:1:2 sdo  8:224   [ready ][active]

1IBM_____2105____________72722206
[size=19 GB][features="0"][hwhandler="0"]
\_ round-robin 0 [active]
  \_ 0:0:0:3 sdd  8:48    [ready ][active]
  \_ 1:0:0:3 sdl  8:176   [ready ][active]
  \_ 1:0:1:3 sdp  8:240   [ready ][active]

The devs that fall out have been blacklisted:
---------------------------------------------
[root@pecan ~]# multipath  -v3 -d | grep blacklist
dm-0 blacklisted
dm-1 blacklisted
dm-2 blacklisted
dm-3 blacklisted
dm-4 blacklisted
dm-5 blacklisted
fd0 blacklisted
hda blacklisted
hdb blacklisted
hdc 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
sdf blacklisted
sdh blacklisted
sdm blacklisted

environment:
 - rhas4 U2 Beta - Linux pecan 2.6.9-16.EL #1 Mon Aug 15 19:58:49 EDT 2005 i686 i686 i386 GNU/Linux
 - multipath-tools-0.4.5.49. compiled from ftp://sources.redhat.com/pub/dm/multipath-tools
    one-off patch of mpath_faker.c
 - 2 QLogic PCI to Fibre Channel Host Adapters for QLA2340:
   Firmware version 3.03.15 IPX, Driver version 8.01.00b5-rh2
 - IBM ESS 2105F20 4 paths
============================================================
Ray Stell  stellr@vt.edu  (540) 231-4109  Tempus fugit  28^D

Re: blacklisted paths?

[Mike Anderson]

Ray Stell <stellr@cns.vt.edu> wrote:
> [root@pecan ~]# multipath  -v3 -d | grep blacklist
> dm-0 blacklisted
> dm-1 blacklisted
> dm-2 blacklisted
> dm-3 blacklisted
> dm-4 blacklisted
> dm-5 blacklisted
> fd0 blacklisted
> hda blacklisted
> hdb blacklisted
> hdc 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
> sdf blacklisted
> sdh blacklisted
> sdm blacklisted

Well I do not have a good explanation why the blacklisting is not more
consistent, but can you send your /etc/multipath.conf. I might suspect
that a devnode_blacklist regular expression maybe matching resulting in
blacklisting when it should not.


-andmike
--
Michael Anderson
andmike@us.ibm.com

Re: blacklisted paths?

[Ray Stell]

On Mon, 19 Sep 2005 16:07:18 -070, Mike Anderson wrote:
>Well I do not have a good explanation why the blacklisting is not more
>consistent, but can you send your /etc/multipath.conf. I might suspect
>that a devnode_blacklist regular expression maybe matching resulting in
>blacklisting when it should not.

Thanks for looking at this problem:

# cat /etc/multipath.conf
# Blacklist all devices by default. Remove this to enable multipathing
# on the default devices.
##
## This is a template multipath-tools configuration file
## Uncomment the lines relevent to your environment
##
defaults {
        multipath_tool  "/sbin/multipath -v0"
        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"
        default_features        "0"
        rr_wmin_io              100
        failback                immediate
}
devnode_blacklist {
        devnode "hd*"
        devnode "fd*"
        devnode "ram*"
        devnode "md*"
}
devices {
        device {
                vendor                  "IBM     "
                product                 "2105            "
                path_grouping_policy    multibus
                path_checker            tur
        }
}
============================================================
Ray Stell  stellr@vt.edu  (540) 231-4109  Tempus fugit  28^D

Re: blacklisted paths?

[Ray Stell]

On Tue, Sep 20, 2005 at 08:01:53AM -0400, Ray Stell wrote:
> devnode_blacklist {
>         devnode "hd*"
>         devnode "fd*"
>         devnode "ram*"
>         devnode "md*"
> }

I removed the * chars from this block it mapped all the paths.  
============================================================
Ray Stell  stellr@vt.edu  (540) 231-4109  Tempus fugit  28^D

Re: Re: blacklisted paths?

[Mike Anderson]

Ray Stell <stellr@cns.vt.edu> wrote:
> On Tue, Sep 20, 2005 at 08:01:53AM -0400, Ray Stell wrote:
> > devnode_blacklist {
> >         devnode "hd*"
> >         devnode "fd*"
> >         devnode "ram*"
> >         devnode "md*"
> > }
> 
> I removed the * chars from this block it mapped all the paths.  

Good to see that they are all mapped now. You may want to switch to using
"^" to match beginning of line and also use the multiple match / single
line regular expression.

Here is an example of what I am running. I believe it is close to the
/etc/multipath.conf example file.

devnode_blacklist {
        devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*"
        devnode "^hd[a-z][0-9]*"
        devnode "^cciss!c[0-9]d[0-9]*[p[0-9]*]"
}

-andmike
--
Michael Anderson
andmike@us.ibm.com