[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [dm-devel] Blacklist broken?



Title: Re: [dm-devel] Blacklist broken?

Doing a bit more checking, I can’t get multipath to let go.

Added this to multipath.conf:
blacklist {
        devnode "*"
}

devnode_blacklist {
        devnode "*"
        wwid 36001ec90ee4ee600105ac65e04e84e61
#       wwid 36001e4f02bc746000f60789e05a38474
        devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*"
        devnode "^hd[a-z]"
        devnode "^cciss!c[0-9]d[0-9]*"
        devnode "/dev/sda"
        devnode "/dev/sda1"
        devnode "/dev/disk/by-uuid/8ed92bb6-0ddb-4fbc-907d-fdf12e5550a3"
}

Yet it just comes back.

[root bonjovi ~]# multipath -ll
mpath0 (36001ec90ee4ee600105ac65e04e84e61) dm-0 DELL,PERC 6/i
size=279G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=1 status=active
  `- 2:2:0:0 sda 8:0 active ready running

I find this particularly amusing from multipath -v3:

===== no paths =====
Jul 14 16:31:50 | params = 0 0 1 1 round-robin 0 1 1 8:0 100
Jul 14 16:31:50 | status = 2 0 0 0 1 1 A 0 1 0 8:0 A 0
Jul 14 16:31:50 | 8:0: not found in pathvec
Jul 14 16:31:50 | sda: mask = 0x1f
Jul 14 16:31:50 | sda: dev_t = 8:0
Jul 14 16:31:50 | sda: size = 584843264
Jul 14 16:31:50 | sda: subsystem = scsi
Jul 14 16:31:50 | sda: vendor = DELL
Jul 14 16:31:50 | sda: product = PERC 6/i
Jul 14 16:31:50 | sda: rev = 1.11
Jul 14 16:31:50 | sda: h:b:t:l = 2:2:0:0
Jul 14 16:31:50 | sda: serial = 00614ee8045ec65a1000e64eee90ec01
Jul 14 16:31:50 | sda: get_state
Jul 14 16:31:50 | loading /lib64/multipath/libchecktur.so checker
Jul 14 16:31:50 | sda: path checker = tur (config file default)
Jul 14 16:31:50 | sda: checker timeout = 300000 ms (internal default)
Jul 14 16:31:50 | sda: state = running
Jul 14 16:31:50 | sda: state = 3
Jul 14 16:31:50 | sda: prio = const (config file default)
Jul 14 16:31:50 | sda: const prio = 1
Jul 14 16:31:50 | sda: (DELL:PERC 6/i) device node name blacklisted

And:
[root bonjovi ~]# multipath -v4 | grep sda
Jul 14 16:32:42 | Discover device /sys/block/sda
Jul 14 16:32:42 | sda: device node name blacklisted
Jul 14 16:32:42 | sda: mask = 0x1f
Jul 14 16:32:42 | sda: dev_t = 8:0
Jul 14 16:32:42 | sda: size = 584843264
Jul 14 16:32:42 | sda: subsystem = scsi
Jul 14 16:32:42 | sda: vendor = DELL
Jul 14 16:32:42 | sda: product = PERC 6/i
Jul 14 16:32:42 | sda: rev = 1.11
Jul 14 16:32:42 | sda: h:b:t:l = 2:2:0:0
Jul 14 16:32:42 | sda: serial = 00614ee8045ec65a1000e64eee90ec01
Jul 14 16:32:42 | sda: get_state
Jul 14 16:32:42 | sda: path checker = tur (config file default)
Jul 14 16:32:42 | sda: checker timeout = 300000 ms (internal default)
Jul 14 16:32:42 | sda: state = running
Jul 14 16:32:42 | sda: state = 3
Jul 14 16:32:42 | sda: prio = const (config file default)
Jul 14 16:32:42 | sda: const prio = 1
Jul 14 16:32:42 | sda: (DELL:PERC 6/i) device node name blacklisted

So it’s not as if multipath doesn’t know that sda should be blacklisted.  It just doesn’t care.

On 7/14/11 4:06 PM, "Brian Stamper" <brian p stamper nasa gov> wrote:

I just upgrade an FC13 system to FC15, and now multipath is grabbing the system drive before the normal fsck can run, which is causing the machine to not boot.  I get the message: “Filesystem mounted or opened exclusively by another program? “  Now, I can simply control-d to continue, but why is multipath grabbing the drive?  I’ve blacklisted it every way I can, using devnode, using wwid, it simply ignores it and continues to create a path map for /dev/sda.

device-mapper-1.02.63-3.fc15.x86_64
device-mapper-multipath-0.4.9-15.fc15.x86_64
device-mapper-libs-1.02.63-3.fc15.x86_64

2.6.38.8-35.fc15.x86_64

mpath0 (36001ec90ee4ee600105ac65e04e84e61) dm-0 DELL,PERC 6/i
size=279G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=1 status=active
  `- 2:2:0:0  sda 8:0   active ready running

[root bonjovi ~]# blkid | grep boot
/dev/sda1: LABEL="/boot" UUID="8ed92bb6-0ddb-4fbc-907d-fdf12e5550a3" TYPE="ext3" SEC_TYPE="ext2"
/dev/mapper/mpath0p1: LABEL="/boot" UUID="8ed92bb6-0ddb-4fbc-907d-fdf12e5550a3" TYPE="ext3"

>From multipath.conf:

blacklist {
        wwid 36001ec90ee4ee600105ac65e04e84e61
        devnode "/dev/sda"
        devnode "/dev/sda1"
}
devnode_blacklist {
        wwid 36001ec90ee4ee600105ac65e04e84e61
        devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*"
        devnode "^hd[a-z]"
        devnode "^cciss!c[0-9]d[0-9]*"
        devnode “sda”
        devnode “/dev/sda”
}

I’ve even tried blacklisting by /disk/by/uuid.  What does it take to get multipath to quit grabbing this disk?

-brian

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]