* Trying to blacklist a USB memory stick
@ 2006-07-14 14:38 Bruen, Mark
0 siblings, 0 replies; 3+ messages in thread
From: Bruen, Mark @ 2006-07-14 14:38 UTC (permalink / raw)
To: device-mapper development
I'm trying to blacklist a USB memory stick in /etc/multipath.conf. The
output of multipath -v4:
===== path sdar =====
bus = 1
dev_t = 66:176
size = 126976
vendor =
product = USB DISK 2.0
rev = 1.16
h:b:t:l = 3:0:0:0
tgt_node_name =
failed to open /dev/sdar
I've tried this with the "h:b:t:l" alone and with the "product" alone
(neither work):
devnode_blacklist {
# devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st|sda|sdb|hdc)[0-9]*"
devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st|hdc)[0-9]*"
devnode "sda "
devnode "sdb "
wwid 350002ac0001302c6
wwid 350002ac0002502c6
device {
h:b:t:l = 3:0:0:0
product "USB DISK 2.0"
}
}
Any ideas? Thanks.
-Mark
^ permalink raw reply [flat|nested] 3+ messages in thread
* RE: Trying to blacklist a USB memory stick
@ 2008-09-30 10:47 Harald_Jensas
2008-09-30 14:23 ` Konrad Rzeszutek
0 siblings, 1 reply; 3+ messages in thread
From: Harald_Jensas @ 2008-09-30 10:47 UTC (permalink / raw)
To: dm-devel
Hi,
I just subscribed to the list, I am an enterprise deployment engineer at Dell and do frequently work with device-mapper-multipath. A few weeks back I configured the SAN storage for 4 RHEL 5 servers that will be an Oracle RAC cluster. Now the customer plugged an USB key into 2 of the systems, and he noticed that device-mapper-multipath creates a device and adds a binding to /var/lib/multipath/bindings.
Att: Mark Bruen
Did you ever solve your problem?
I was thinking of doing something like this as a solution:
blacklist {
wwid *
devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*"
devnode "^hd[a-z]"
}
blacklist_exceptions {
wwid <WWID>
wwid <WWID>
wwid <WWID>
}
E.g blacklist all wwid's as default, then specifically add an exception for each wwid that go with a "storage address space" that I want to use Multipath to manage. It is a bit more administrative overhead, but it will allow strict control of what devices dm-mp is controlling.
Another idea is to blacklist all devices, and make exceptions for the device I want Multipath to control:
blacklist {
device {
vendor "*"
product "*"
}
devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*"
devnode "^hd[a-z]"
}
blacklist_exceptions {
device {
vendor "DGC"
product "*"
}
}
Comments appreciated.
Thanks!
--
Harald Jensås
Dell EDT | NER (Sweden)
-------------------------------------------------------------------------------------
* From: "Bruen, Mark" <mbruen trilegiant com>
* To: device-mapper development <dm-devel redhat com>
* Subject: [dm-devel] Trying to blacklist a USB memory stick
* Date: Fri, 14 Jul 2006 10:38:33 -0400
I'm trying to blacklist a USB memory stick in /etc/multipath.conf. The output of multipath -v4:
===== path sdar =====
bus = 1
dev_t = 66:176
size = 126976
vendor = product = USB DISK 2.0 rev = 1.16
h:b:t:l = 3:0:0:0
tgt_node_name =
failed to open /dev/sdar
I've tried this with the "h:b:t:l" alone and with the "product" alone (neither work):
devnode_blacklist {
# devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st|sda|sdb|hdc)[0-9]*"
devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st|hdc)[0-9]*"
devnode "sda "
devnode "sdb "
wwid 350002ac0001302c6
wwid 350002ac0002502c6
device {
h:b:t:l = 3:0:0:0
product "USB DISK 2.0"
}
}
Any ideas? Thanks.
-Mark
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Trying to blacklist a USB memory stick
2008-09-30 10:47 Harald_Jensas
@ 2008-09-30 14:23 ` Konrad Rzeszutek
0 siblings, 0 replies; 3+ messages in thread
From: Konrad Rzeszutek @ 2008-09-30 14:23 UTC (permalink / raw)
To: device-mapper development
On Tue, Sep 30, 2008 at 12:47:34PM +0200, Harald_Jensas@Dell.com wrote:
> Hi,
>
> I just subscribed to the list, I am an enterprise deployment engineer at Dell and do frequently work with device-mapper-multipath. A few weeks back I configured the SAN storage for 4 RHEL 5 servers that will be an Oracle RAC cluster. Now the customer plugged an USB key into 2 of the systems, and he noticed that device-mapper-multipath creates a device and adds a binding to /var/lib/multipath/bindings.
>
You can also edit the udev rules (or add a new one) that will make your USB devices be ignored by
multipath daemon. This will effectivly ignore _any_ USB device.
Look for example for 40-redhat.rules and 'man udev' on how to configure your own rules.
Here is an example where the linear maps don't ever get to the multipathd daemon:
#Weed out the linear map.
KERNEL=="dm-*", PROGRAM=="/sbin/dmsetup table -j %M -m %m", RESULT=="*linear*", OPTIONS="last_rule"
# And block devices that come from usb:
ACTION=="add", KERNEL=="sd*", SUBSYSTEM=="usb", OPTIONS="last_rule"
This of course being before the, catch-it-all rule:
RUN+="socket:/org/kernel/dm/multipath_event"
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2008-09-30 14:23 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-07-14 14:38 Trying to blacklist a USB memory stick Bruen, Mark
-- strict thread matches above, loose matches on Subject: below --
2008-09-30 10:47 Harald_Jensas
2008-09-30 14:23 ` Konrad Rzeszutek
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.