From: "Benjamin Marzinski" <bmarzins@redhat.com>
To: Hannes Reinecke <hare@suse.de>
Cc: dm-devel@redhat.com
Subject: multipath.rules placement
Date: Tue, 8 Nov 2016 13:56:25 -0600 [thread overview]
Message-ID: <20161108195625.GQ1972@octiron.msp.redhat.com> (raw)
I'm looking through the multipath udev rules again to see if we can come
closer to one consistent set, or at least understand why we need to
agree to disagree and right now I'm trying to figure out why it's
important for SUSE to have 56-multipath.rules run before
60-persistent-storage.rules.
We use 62-multipath.rules in RHEL for two main reasons. First, scsi_id
is run in 60-persistent-storage.rules, which is what sets ID_SERIAL, so
if multipath.rules is run before that, we'll never be able to get our
information from udev. I know that you've added code to cope with this,
assuming the standard uid_attribute, but it seems better to me to just
wait for udev to fill in these values itself.
Second, 60-persistent-storage.rules runs blkid, which should set
ID_FS_TYPE. Setting it in 56-multipath.rules just means that
60-persistent-storage.rules will overwrite it.
So, what do we gain by running multipath.rules before
60-persistent-storage.rules?
-Ben
next reply other threads:[~2016-11-08 19:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-08 19:56 Benjamin Marzinski [this message]
2016-11-09 7:52 ` multipath.rules placement 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=20161108195625.GQ1972@octiron.msp.redhat.com \
--to=bmarzins@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.