diff options
| author | Mariusz Tkaczyk <mariusz.tkaczyk@intel.com> | 2020-04-08 16:44:52 +0200 |
|---|---|---|
| committer | Jes Sorensen <jsorensen@fb.com> | 2020-04-27 10:23:35 -0400 |
| commit | e1b92ee0de26576a33b20c9dd6ef6bd8cab8e283 (patch) | |
| tree | f0315a60016b27e932558b608afd2a162841ba3e | |
| parent | ba1b3bc80ea555c288f1119e69d9273249967081 (diff) | |
| download | mdadm-e1b92ee0de26576a33b20c9dd6ef6bd8cab8e283.tar.gz | |
udev: Ignore change event for imsm
When adding a device to a container mdadm has to close its file
descriptor before sysfs_add_disk(). This generates change event.
There is race possibility because metadata is already written and other
-I process can place drive differently. As a result device can be added
to two containers simultaneously.
From IMSM perspective there is no need to react for change event. IMSM
doesn't support stacked devices.
Signed-off-by: Mariusz Tkaczyk <mariusz.tkaczyk@intel.com>
Signed-off-by: Jes Sorensen <jsorensen@fb.com>
| -rw-r--r-- | udev-md-raid-assembly.rules | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/udev-md-raid-assembly.rules b/udev-md-raid-assembly.rules index 9f055ed0..d668cddd 100644 --- a/udev-md-raid-assembly.rules +++ b/udev-md-raid-assembly.rules @@ -23,7 +23,7 @@ IMPORT{cmdline}="nodmraid" ENV{nodmraid}=="?*", GOTO="md_inc_end" ENV{ID_FS_TYPE}=="ddf_raid_member", GOTO="md_inc" ENV{noiswmd}=="?*", GOTO="md_inc_end" -ENV{ID_FS_TYPE}=="isw_raid_member", GOTO="md_inc" +ENV{ID_FS_TYPE}=="isw_raid_member", ACTION!="change", GOTO="md_inc" GOTO="md_inc_end" LABEL="md_inc" |