* Multipath blacklisted devices
@ 2006-04-20 17:57 URZ- AG
2006-04-20 20:21 ` Christophe Varoqui
0 siblings, 1 reply; 3+ messages in thread
From: URZ- AG @ 2006-04-20 17:57 UTC (permalink / raw)
To: device-mapper development
Hi,
I'm using the latest git version of multipath-tools with a 2.6.16 kernel.
Today I've tried to blacklist a scsi device in the multipath.conf file
using the following entry:
devnode "^(sda)[0-9]*"
This didn't work at all, it seems that multipath doesn't use the
blacklist entries found in multipatch.conf.
I've patched the source code to hardcode that device and this works well.
I've tried to debug the config loading but my C knowledge is too poor
and I haven't been able to find out whats wrong so far.
Any help for debugging would be greatly apreciated, I've tried to write
some code which dumps all entries read from the config file but it
didn't work so far.
Thanks for your time and great work,
Arsène
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: Multipath blacklisted devices
2006-04-20 17:57 Multipath blacklisted devices URZ- AG
@ 2006-04-20 20:21 ` Christophe Varoqui
2006-04-22 11:49 ` Arsene Gschwind
0 siblings, 1 reply; 3+ messages in thread
From: Christophe Varoqui @ 2006-04-20 20:21 UTC (permalink / raw)
To: device-mapper development
URZ- AG a écrit :
> Hi,
>
> I'm using the latest git version of multipath-tools with a 2.6.16 kernel.
> Today I've tried to blacklist a scsi device in the multipath.conf file
> using the following entry:
> devnode "^(sda)[0-9]*"
>
> This didn't work at all, it seems that multipath doesn't use the
> blacklist entries found in multipatch.conf.
> I've patched the source code to hardcode that device and this works well.
> I've tried to debug the config loading but my C knowledge is too poor
> and I haven't been able to find out whats wrong so far.
> Any help for debugging would be greatly apreciated, I've tried to
> write some code which dumps all entries read from the config file but
> it didn't work so far.
>
> Thanks for your time and great work,
> Arsène
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
>
It works here :(
Try to extract the live blacklist with :
# multipathd/multipathd -k"show conf"
...
blacklist {
devnode ^(sda)[0-9]*
devnode ^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*
devnode ^hd[a-z]
devnode ^cciss!c[0-9]d[0-9]*
wwid 26353900f02796769
device {
vendor IET
product A.*A
}
device {
vendor DGC
product LUNZ
}
}
...
Regards,
cvaroqui
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: Multipath blacklisted devices
2006-04-20 20:21 ` Christophe Varoqui
@ 2006-04-22 11:49 ` Arsene Gschwind
0 siblings, 0 replies; 3+ messages in thread
From: Arsene Gschwind @ 2006-04-22 11:49 UTC (permalink / raw)
To: device-mapper development
Hi Christophe,
I've found the problem, my entry in multipath.conf was devnode_blacklist
{ } and it should be only blacklist{}.
You may have to correct multipath.conf.synthetic provided by the tarball
( and the git version) because I've used that file to create my own and
it includes this error.
Thanks a lot for your help and work
Arsène
Christophe Varoqui wrote:
> URZ- AG a écrit :
>
>> Hi,
>>
>> I'm using the latest git version of multipath-tools with a 2.6.16
>> kernel.
>> Today I've tried to blacklist a scsi device in the multipath.conf
>> file using the following entry:
>> devnode "^(sda)[0-9]*"
>>
>> This didn't work at all, it seems that multipath doesn't use the
>> blacklist entries found in multipatch.conf.
>> I've patched the source code to hardcode that device and this works
>> well.
>> I've tried to debug the config loading but my C knowledge is too poor
>> and I haven't been able to find out whats wrong so far.
>> Any help for debugging would be greatly apreciated, I've tried to
>> write some code which dumps all entries read from the config file but
>> it didn't work so far.
>>
>> Thanks for your time and great work,
>> Arsène
>>
>> --
>> dm-devel mailing list
>> dm-devel@redhat.com
>> https://www.redhat.com/mailman/listinfo/dm-devel
>>
> It works here :(
> Try to extract the live blacklist with :
>
> # multipathd/multipathd -k"show conf"
> ...
> blacklist {
> devnode ^(sda)[0-9]*
> devnode ^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*
> devnode ^hd[a-z]
> devnode ^cciss!c[0-9]d[0-9]*
> wwid 26353900f02796769
> device {
> vendor IET
> product A.*A
> }
> device {
> vendor DGC
> product LUNZ
> }
> }
> ...
>
> Regards,
> cvaroqui
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
--
***********************************************************
Gschwind Arsene
Universitaet Rechenzentrum (URZ)
Klingelbergstrasse 70
CH-4056 Basel
SWITZERLAND
Languages : F/E/D
WWW: <http://www.urz.unibas.ch>
Mail: <Arsene DOT Gschwind AT unibas DOT ch>
************************************************************
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2006-04-22 11:49 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-04-20 17:57 Multipath blacklisted devices URZ- AG
2006-04-20 20:21 ` Christophe Varoqui
2006-04-22 11:49 ` Arsene Gschwind
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.