Re: multipathd removing DM devices that don't belong to it

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

 



Hi Ben,

Unfortunately, I missed your response two months ago. Somehow it didn’t get to my mailbox. Found it on the web. I would like to revisit this question.

 

I think I understood your explanation. Our proposal is to add an ignore_multipaths section to multipath.conf that looks like the following:

 

ignore_multipaths

{

    name "flashgrid*"

}

 

This example should prevent multipathd from touching any DM devices with names starting with ‘flashgrid’

The justification is that this will allow custom implementations of multipath management that also use dmsetup and that can co-exist on the same system with multipathd.

 

Is this possible to do? We will be happy to do testing.

 

Thank you!

-Artem

 

 


  • From: "Benjamin Marzinski" <bmarzins redhat com>
  • To: device-mapper development <dm-devel redhat com>
  • Subject: Re: multipathd removing DM devices that don't belong to it
  • Date: Mon, 22 Jun 2015 11:04:38 -0500

On Tue, Jun 16, 2015 at 10:02:23PM +0000, Artem Danielov wrote:
>    Hello,
> 
>    Looking for an advice on whether this is an expected behavior or a bug.
> 
>    device-mapper-multipath-0.4.9-77.el7.x86_64
> 
>     
> 
>    When multipathd service starts it will remove any DM devices with
>    multipath target, even if the underlying devices are blacklisted.
> 
>    We are trying to use dmsetup directly  to implement custom multipath
>    management logic separate from multipathd. But unfortunately if multipathd
>    is present and enabled it removes DM devices with multipath target that we
>    create.
> 
>     
> 
>    Is this a bug?
 
I don't know if I'd call it a bug. It is certainly how multipath is
designed to work.  The issue is this.  When you start multipathd up do a
reconfigure.  It doesn't know if the configuration has changed. So, if
there are devices configured and it doesn't think they should be, it
assumes that you've changed your configuration, and you'd like it to use
your current configuration, which means removing devices that no longer
are allowed.
 
I don't see any way of making this work, without adding a section to the
multipath.conf file to ignore devices with certain wwids entirely (which
is different from blacklisting them).
 
-Ben
 
> 
>     
> 
>    Thanks for your help!
> 
>     
> 
>    Artem Danielov | Chief Technology Officer | FlashGrid Inc. |
>    [1]artem flashgrid io | +1-503-568-5249
> 
>     
> 
> References
> 
>    Visible links
>    1. mailto:artem flashgrid io
 
> --
> dm-devel mailing list
> dm-devel redhat com
> https://www.redhat.com/mailman/listinfo/dm-devel
 

 

--
dm-devel mailing list
dm-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/dm-devel

[Index of Archives]     [DM Crypt]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Packaging]     [Fedora SELinux]     [Yosemite Discussion]     [KDE Users]     [Fedora Docs]

  Powered by Linux