From: Michal Soltys <soltys@ziu.info>
To: neilb@suse.de
Cc: linux-raid@vger.kernel.org
Subject: [PATCH 1/2] udev rules: don't incrementally autoassemble everything
Date: Sun, 4 Sep 2011 14:42:43 +0200 [thread overview]
Message-ID: <1315140164-6991-2-git-send-email-soltys@ziu.info> (raw)
In-Reply-To: <1315140164-6991-1-git-send-email-soltys@ziu.info>
All native and imsm arrays were autoassembled unconditionally (excluding
forgotten ddf containers).
This caused few issues:
- mdadm.conf configuration irrelevant - container or not - everything
was assembled as soon as any component device was found during the boot
- problems with any 65-md-inc* rules often present, that also allow
more fine-grained control - e.g. dracut's ones allow incremental assembly
limited to certain uuids
Signed-off-by: Michal Soltys <soltys@ziu.info>
---
udev-md-raid.rules | 2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/udev-md-raid.rules b/udev-md-raid.rules
index c2105bc..02172de 100644
--- a/udev-md-raid.rules
+++ b/udev-md-raid.rules
@@ -5,10 +5,8 @@ SUBSYSTEM!="block", GOTO="md_end"
# handle potential components of arrays
ENV{ID_FS_TYPE}=="linux_raid_member", ENV{ID_PATH}!="", ACTION=="remove", RUN+="/sbin/mdadm -If $name --path $env{ID_PATH}"
ENV{ID_FS_TYPE}=="linux_raid_member", ENV{ID_PATH}=="", ACTION=="remove", RUN+="/sbin/mdadm -If $name"
-ENV{ID_FS_TYPE}=="linux_raid_member", ACTION=="add", RUN+="/sbin/mdadm --incremental $env{DEVNAME}"
ENV{ID_FS_TYPE}=="isw_raid_member", ENV{ID_PATH}!="", ACTION=="remove", RUN+="/sbin/mdadm -If $name --path $env{ID_PATH}"
ENV{ID_FS_TYPE}=="isw_raid_member", ENV{ID_PATH}=="", ACTION=="remove", RUN+="/sbin/mdadm -If $name"
-ENV{ID_FS_TYPE}=="isw_raid_member", ACTION=="add", RUN+="/sbin/mdadm --incremental $env{DEVNAME}"
# handle md arrays
ACTION!="add|change", GOTO="md_end"
--
1.7.5.3
next prev parent reply other threads:[~2011-09-04 12:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-04 12:42 [PATCH 0/2] udev rules behaviour Michal Soltys
2011-09-04 12:42 ` Michal Soltys [this message]
2011-09-04 12:42 ` [PATCH 2/2] shorten remove rules Michal Soltys
2011-09-06 21:39 ` v2 - keep incremental, check types Michal Soltys
2011-09-06 21:39 ` [PATCH] udev rules: add ddf, shorten checks, use $tempnode Michal Soltys
2011-09-07 4:00 ` [PATCH 0/2] udev rules behaviour NeilBrown
2011-09-08 7:25 ` v2 once more, for current head Michal Soltys
2011-09-08 7:25 ` [PATCH] udev rules: use $tempnode, check for supported types, comments Michal Soltys
2011-09-19 3:12 ` NeilBrown
2011-09-19 7:23 ` Michal Soltys
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=1315140164-6991-2-git-send-email-soltys@ziu.info \
--to=soltys@ziu.info \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).