Linux Device Mapper development
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: Peter Volkov <peter.volkov@gmail.com>, dm-devel@redhat.com
Subject: Re: multipath-0.5.0 still provides broken udev rules
Date: Mon, 25 Apr 2016 17:04:30 +0200	[thread overview]
Message-ID: <571E31FE.5090004@suse.de> (raw)
In-Reply-To: <CAE+k_g+Eh3H1EAiJ0jm7P-efGbOOwpWRtYmvXyR9qhhHtefV7g@mail.gmail.com>

On 04/25/2016 12:52 PM, Peter Volkov wrote:
> Hi, guys.
> 
> There is a problem: udev does not create partitions for multipath
> devices in case I use kpartx.rules provided with multipath sources.
> I found that udev always go to kpartx_end after following line of rules:
> ENV{DM_TABLE_STATE}!="LIVE", GOTO="kpartx_end"
> 
> There is 8 (!!!) years old thread that discusses this problem:
> https://www.redhat.com/archives/dm-devel/2007-July/msg00095.html
> 
> So what is the current state? Should we fix udev rules for multipath
> or should we create better patch for dmsetup.c? Meanwhile I've
> copied multipath.rules from redhat and partitions are created as
> they should.
> 
> 
Sigh. I really need to post my multipath update.
Stay tuned.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		   Teamlead Storage & Networking
hare@suse.de			               +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (AG Nürnberg)

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

      parent reply	other threads:[~2016-04-25 15:04 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-25 10:52 multipath-0.5.0 still provides broken udev rules Peter Volkov
2016-04-25 10:58 ` Zdenek Kabelac
2016-04-25 12:10   ` Peter Volkov
2016-04-25 12:32     ` Zdenek Kabelac
2016-04-25 12:52       ` Peter Volkov
2016-04-25 12:56       ` Christophe Varoqui
2016-04-25 14:15         ` Peter Volkov
2016-04-25 17:38         ` Benjamin Marzinski
2016-04-26  5:43           ` Hannes Reinecke
2016-04-26  8:39             ` Zdenek Kabelac
2016-04-26  8:47               ` Hannes Reinecke
2016-04-26  9:19                 ` Zdenek Kabelac
2016-04-25 20:14         ` Xose Vazquez Perez
2016-04-26  5:53           ` Hannes Reinecke
2016-04-27 22:46             ` Benjamin Marzinski
2016-04-28  6:23               ` Hannes Reinecke
2016-04-28 22:10                 ` Benjamin Marzinski
2016-05-11 18:46                   ` Distributions mpt code Xose Vazquez Perez
2016-04-28 22:45                 ` multipath-0.5.0 still provides broken udev rules Benjamin Marzinski
2016-05-19 15:24               ` multipath-tools: irrelevant files Xose Vazquez Perez
2016-06-01 15:05                 ` Christophe Varoqui
2016-06-04  0:14                   ` multipath-tools: web Xose Vazquez Perez
2016-04-25 15:04 ` Hannes Reinecke [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=571E31FE.5090004@suse.de \
    --to=hare@suse.de \
    --cc=dm-devel@redhat.com \
    --cc=peter.volkov@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox