From: NeilBrown Date: Tue, 3 Oct 2006 08:15:58 +0000 (-0700) Subject: [PATCH] md: fix duplicity of levels in md.txt X-Git-Tag: v2.6.19-rc1~238 X-Git-Url: http://pilppa.com/gitweb/?a=commitdiff_plain;h=d33a56d3639eba077489c937943a32ef6237b1b8;p=linux-2.6-omap-h63xx.git [PATCH] md: fix duplicity of levels in md.txt md.txt has two sections describing the 'level' sysfs attribute, and some of the text is out-of-date. So make just one section, and make it right. Cc: Christian Kujau Signed-off-by: Neil Brown Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds --- diff --git a/Documentation/md.txt b/Documentation/md.txt index 084ecf4eb2f..9ae9e407898 100644 --- a/Documentation/md.txt +++ b/Documentation/md.txt @@ -154,11 +154,12 @@ contains further md-specific information about the device. All md devices contain: level - a text file indicating the 'raid level'. This may be a standard - numerical level prefixed by "RAID-" - e.g. "RAID-5", or some - other name such as "linear" or "multipath". + a text file indicating the 'raid level'. e.g. raid0, raid1, + raid5, linear, multipath, faulty. If no raid level has been set yet (array is still being - assembled), this file will be empty. + assembled), the value will reflect whatever has been written + to it, which may be a name like the above, or may be a number + such as '0', '5', etc. raid_disks a text file with a simple number indicating the number of devices @@ -192,14 +193,6 @@ All md devices contain: 1.2 (newer format in varying locations) or "none" indicating that the kernel isn't managing metadata at all. - level - The raid 'level' for this array. The name will often (but not - always) be the same as the name of the module that implements the - level. To be auto-loaded the module must have an alias - md-$LEVEL e.g. md-raid5 - This can be written only while the array is being assembled, not - after it is started. - layout The "layout" for the array for the particular level. This is simply a number that is interpretted differently by different