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

Re: [dm-devel] Multipath blacklist exceptions issues

Hi Ben,

On Tue, 13 Nov 2007 14:18:04 -0600, Benjamin Marzinski <bmarzins redhat com> wrote:
> multipath will suddenly start spitting out warning messages.  This is
> another issue that would be solved by having an invalid_drivers section.

I agree with separating those filters.
Those filters are used for different purposes, one is to avoid
the getuid callout, the other is to decide whether use the device
for multipath.
Merging those different purpose filters into one structure will mess
things up.

I think that the following rule which you proposed is simple enough:
  o unneeded devices are dropped first by the invalid_drivers section
  o First match of the filter section is used for each device like LVM2

> Finally, you mentioned devnode rules.  Do you think that they are
> necessary?  The purpose of the driver rules is to replace the devnode
> rules with ones that don't allow users to do things like
> blacklist {
> 	devnode "sdc"
> }
> which can be done other ways, and might end up doing the wrong thing
> later if their device names change.

Although I'm not sure it's necessary, I prefer to leave it.
I sometimes use devnode rules just for testing, like creating a map
including only a part of paths (not all-paths).
That sort of mapping is not possible without devnode rule now.

Kiyoshi Ueda

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