All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zdenek Kabelac <zkabelac@redhat.com>
To: dm-devel@redhat.com, Hannes Reinecke <hare@suse.de>
Subject: Re: multipath-0.5.0 still provides broken udev rules
Date: Tue, 26 Apr 2016 11:19:33 +0200	[thread overview]
Message-ID: <571F32A5.7090405@redhat.com> (raw)
In-Reply-To: <571F2B3C.5040306@suse.de>

On 26.4.2016 10:47, Hannes Reinecke wrote:
> On 04/26/2016 10:39 AM, Zdenek Kabelac wrote:
>> On 26.4.2016 07:43, Hannes Reinecke wrote:
>>> On 04/25/2016 07:38 PM, Benjamin Marzinski wrote:
>>>> On Mon, Apr 25, 2016 at 02:56:35PM +0200, Christophe Varoqui wrote:
>>>>>      Hi,
>>>>>      Those example udev rules are indeed unmaintained and should
>>>>> be removed not
>>>>>      to confuse distributors.
>>>>>      Distributors can't be asked to agree on a common udev
>>>>> ruleset. Ben,
>>>>>      Hannes, Xosé, Peter are you ok with my deleting the udev
>>>>> rules example ?
>>>>
>>>> I am personally fine with kpartx.rules being deleted. Red Hat
>>>> doesn't
>>>> package it.
>>>>
>>> Well, we do. We use kpartx to generate partitions for multipath and
>>> dmraid, so we do need this rule.
>>> Please do not delete it; if so I will only have to re-add it again
>>> in a SUSE-specific patch.
>>
>> Hi
>>
>> Can you please elaborate what is the 'specific' need of SUSE for patch?
>>
>> AFAIK there should be no need for it - all identifiers are not
>> tracked by
>> 10-dm.rules
>>
>> It has whole logic about device state built-in.
>>
>> So what exactly would you need to trace in kpartx.rules ?
>>
> We use kpartx.rules to call 'kpartx' itself for creating the
> partition devices on top of any multipath or dmraid devices.
>
> If that logic has been moved into other, generic, device-mapper
> rules please let me know.
> But until then we need the kpartx.rules. file.

Ok, so it seems it is completely chaotic -

As in RHEL/Fedora there is largely hacked  mpath udev rule file,
which is then responsible for using partx?

While in SUSE this seems to be handled by broken old unmaintained  kpartx udev 
rules file (as the file is useless - wondering how could do anything useful on 
SUSE)

AFAIK seems we miss communication between Ben with Hannes here :)

As logically it seem  calling  kpartx rule calls belong to  kpartx package.
However  kpartx upstream rule file is for  systems  from 2007 year.

So I'd have assumed lots of current mpath  RHEL rule patches should be
relocated to kpartx rules.

Leaving this to you guys...

Regards

Zdenek

  reply	other threads:[~2016-04-26  9:19 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 [this message]
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=571F32A5.7090405@redhat.com \
    --to=zkabelac@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=hare@suse.de \
    /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.