diff options
| author | Hannes Reinecke <hare@suse.de> | 2017-03-27 02:15:44 +0200 |
|---|---|---|
| committer | Jes Sorensen <Jes.Sorensen@gmail.com> | 2017-03-28 20:22:32 +0200 |
| commit | 3a77acd7170199adc690332ded37c41f067c720e (patch) | |
| tree | 4b1d9a1068f7cfe3ffca1a25a2ffe8c67f2dd785 /udev-md-raid-assembly.rules | |
| parent | mdadm/bitmap:fixed typos in comments of bitmap.h (diff) | |
| download | mdadm-3a77acd7170199adc690332ded37c41f067c720e.tar.xz mdadm-3a77acd7170199adc690332ded37c41f067c720e.zip | |
udev-md-raid-assembly.rules: Skip non-ready devices
If a device isn't fully initialized (e.g if it should be
handled by multipathing) it should not be considered for
md/RAID auto-assembly. Doing so can cause incorrect results
such as causing multipath to fail during startup.
There is a convention that the udev environment variable
SYSTEMD_READY be set to zero for such devices. So change
the mdadm rules to ignore devices with SYSTEMD_READY==0.
Signed-off-by: Hannes Reinecke <hare@suse.de>
Signed-off-by: NeilBrown <neilb@suse.com>
Signed-off-by: Jes Sorensen <Jes.Sorensen@gmail.com>
Diffstat (limited to 'udev-md-raid-assembly.rules')
| -rw-r--r-- | udev-md-raid-assembly.rules | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/udev-md-raid-assembly.rules b/udev-md-raid-assembly.rules index d0d440a6..8ca232a4 100644 --- a/udev-md-raid-assembly.rules +++ b/udev-md-raid-assembly.rules @@ -7,6 +7,9 @@ ENV{ANACONDA}=="?*", GOTO="md_inc_end" SUBSYSTEM!="block", GOTO="md_inc_end" +# skip non-initialized devices +ENV{SYSTEMD_READY}=="0", GOTO="md_inc_end" + # handle potential components of arrays (the ones supported by md) ENV{ID_FS_TYPE}=="linux_raid_member", GOTO="md_inc" |