From: Zdenek Kabelac <zkabelac@redhat.com>
To: Peter Volkov <peter.volkov@gmail.com>
Cc: dm-devel@redhat.com
Subject: Re: multipath-0.5.0 still provides broken udev rules
Date: Mon, 25 Apr 2016 14:32:58 +0200 [thread overview]
Message-ID: <571E0E7A.4050703@redhat.com> (raw)
In-Reply-To: <CAE+k_gKQcx+QR9bfEp1Wy8BawD14L2G5O0Yw-d0=CffBHqYbrA@mail.gmail.com>
On 25.4.2016 14:10, Peter Volkov wrote:
> On Mon, Apr 25, 2016 at 1:58 PM, Zdenek Kabelac <zkabelac@redhat.com
> <mailto:zkabelac@redhat.com>> wrote:
>
> On 25.4.2016 12:52, Peter Volkov wrote:
>
> 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"
>
>
> Just curious - what would you want to do with inactive table???
>
>
> Actually don't understand what's this table and what's wrong with that. There
> is no traces of DM_TABLE_STATE variable in lvm2 sources. Yet there is such
> variable in udev rules file that comes with multipath sources:
> http://git.opensvc.com/gitweb.cgi?p=multipath-tools/.git;a=blob;f=kpartx/kpartx.rules;h=022361f907e873ac16fc75459b88af34b27576e5;hb=HEAD
So you would need to figure out which rules would have set DM_TABLE_STATE
before ? (I assume such have never existed...)
In Fedora/RHEL these kpartx.rules are not packaged as they are likely some
'ancient' rules - IMHO most of that file is useless on today's distros.
(Unsure about dm-wwn logic???)
So it's rather question for upstream kpartx maintainer why these rules
are not maintained in any way.
Vars like DM_TABLE_STATE are simply not created by dm rules.
kpartx rules comes from year 2007, while dm rules started to be maintained in
2009 - that may explain few things as well...
> That's Gentoo. But I think any distro that uses whatever upstream prepares
> have this problem.
>
> Have you opened any bugzilla anywhere ?
>
>
> Not yet. I'd like to understand what needs to be done first.
>
Likely Gentoo should not install obsoleted udev rules file.
Regards
Zdenek
PS: I could be wrong here - since I've nothing in common with multipath,
so in such case - feel free to correct me....
next prev parent reply other threads:[~2016-04-25 12:32 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 [this message]
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 ` multipath-0.5.0 still provides broken udev rules Hannes Reinecke
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=571E0E7A.4050703@redhat.com \
--to=zkabelac@redhat.com \
--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 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.