diff options
| author | Michal Schmidt <mschmidt@redhat.com> | 2012-07-24 09:47:33 +0200 |
|---|---|---|
| committer | Michal Schmidt <mschmidt@redhat.com> | 2012-07-24 10:01:38 +0200 |
| commit | a96e4839d5ba1b2cbc75d9a998b5f8ccfbb39544 (patch) | |
| tree | 6c16a9ddaa704a479896674bbb8b512ab7e03be0 /rules/99-systemd.rules.in | |
| parent | 81cf1c43c9a24834433bb5c1f0dc6eb3c1c5b44f (diff) | |
rules: avoid mounting raid devices too early
/dev/md0 appears as soon as the first component of the raid array is
added by incremental assembly rules. This is too early for systemd to
attempt to mount the device. The device should be considered plugged
after the raid array becomes active.
https://bugzilla.redhat.com/show_bug.cgi?id=767561
Diffstat (limited to 'rules/99-systemd.rules.in')
| -rw-r--r-- | rules/99-systemd.rules.in | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/rules/99-systemd.rules.in b/rules/99-systemd.rules.in index c117529020..eb8ea0dc97 100644 --- a/rules/99-systemd.rules.in +++ b/rules/99-systemd.rules.in @@ -19,6 +19,9 @@ SUBSYSTEM=="block", KERNEL!="ram*|loop*", ENV{DM_UDEV_DISABLE_OTHER_RULES_FLAG}= SUBSYSTEM=="block", KERNEL!="ram*|loop*", ENV{DM_UUID}=="CRYPT-*", ENV{ID_PART_TABLE_TYPE}=="", ENV{ID_FS_USAGE}=="", ENV{SYSTEMD_READY}="0" +# Ignore raid devices that are not yet assembled and started +SUBSYSTEM=="block", KERNEL=="md*", ATTR{md/array_state}=="|clear|inactive", ENV{SYSTEMD_READY}="0" + # We need a hardware independent way to identify network devices. We # use the /sys/subsystem path for this. Current vanilla kernels don't # actually support that hierarchy right now, however upcoming kernels |