From: David Zeuthen Date: Sun, 15 Feb 2009 06:00:18 +0000 (-0500) Subject: manually import linux-md data since mdadm upstream doesn't do this yet X-Git-Tag: upstream/2.1.2~961 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=f8199852a11d1fb59a90e9e6e00201bbe4fbd65e;p=platform%2Fupstream%2Fudisks2.git manually import linux-md data since mdadm upstream doesn't do this yet --- diff --git a/src/95-devkit-disks.rules b/src/95-devkit-disks.rules index 7fd2c6c..4be161b 100644 --- a/src/95-devkit-disks.rules +++ b/src/95-devkit-disks.rules @@ -59,6 +59,12 @@ LABEL="device_mapper_end" ############################################################################################################## +# pick up data from MD components; this really ought to be done by mdadm itself +# +ENV{ID_FS_TYPE}=="linux_raid_member", IMPORT{program}="/sbin/mdadm --examine --export $tempnode" + +############################################################################################################## + # Example rule for tagging a device with a specific media type. Where and # how to store this database needs some thought. #