aboutsummaryrefslogtreecommitdiffstats
path: root/rules
diff options
context:
space:
mode:
authorKay Sievers <kay.sievers@vrfy.org>2009-02-05 14:03:17 +0100
committerKay Sievers <kay.sievers@vrfy.org>2009-02-05 14:03:17 +0100
commitb822542608326092e177fd1707ca7fb53b2846c4 (patch)
tree2f66b3990480a8b30fae09a32950356ed52e135d /rules
parenta402404fb23195839a9e008dbbe5edb5349c05b0 (diff)
downloadudev-b822542608326092e177fd1707ca7fb53b2846c4.tar.gz
rules: fix md "change"/"remove" handling
On Thu, Feb 5, 2009 at 08:43, Harald Hoyer <harald@redhat.com> wrote: > Radek Vykydal <rvykydal@redhat.com> encountered a problem with md devices. > If the raid is about to be removed a "change" and "remove" event is sent.
Diffstat (limited to 'rules')
-rw-r--r--rules/packages/64-md-raid.rules1
1 files changed, 1 insertions, 0 deletions
diff --git a/rules/packages/64-md-raid.rules b/rules/packages/64-md-raid.rules
index 6fe4d46d..def184f4 100644
--- a/rules/packages/64-md-raid.rules
+++ b/rules/packages/64-md-raid.rules
@@ -11,6 +11,7 @@ KERNEL!="md*", GOTO="md_end"
# container devices have a metadata version of e.g. 'external:ddf' and
# never leave state 'inactive'
ATTR{md/metadata_version}=="external:[A-Za-z]*", ATTR{md/array_state}=="inactive", GOTO="md_ignore_state"
+TEST!="md/array_state", GOTO="md_end"
ATTR{md/array_state}=="|clear|inactive", GOTO="md_end"
LABEL="md_ignore_state"