From: NeilBrown <neilb@suse.de>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org,
Christian Kujau <evil@g-house.de>
Subject: [PATCH 001 of 6] md: Fix duplicity of levels in md.txt
Date: Fri, 29 Sep 2006 12:52:52 +1000 [thread overview]
Message-ID: <1060929025252.15187@suse.de> (raw)
In-Reply-To: 20060929125047.14064.patches@notabene
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 <evil@g-house.de>
Signed-off-by: Neil Brown <neilb@suse.de>
### Diffstat output
./Documentation/md.txt | 17 +++++------------
1 file changed, 5 insertions(+), 12 deletions(-)
diff .prev/Documentation/md.txt ./Documentation/md.txt
--- .prev/Documentation/md.txt 2006-09-29 11:44:38.000000000 +1000
+++ ./Documentation/md.txt 2006-09-29 11:48:54.000000000 +1000
@@ -154,11 +154,12 @@ contains further md-specific information
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
next prev parent reply other threads:[~2006-09-29 2:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-29 2:52 [PATCH 000 of 6] md: Introduction NeilBrown
2006-09-29 2:52 ` NeilBrown [this message]
2006-09-29 2:52 ` [PATCH 002 of 6] md: Remove MAX_MD_DEVS which is an arbitrary limit NeilBrown
2006-09-29 2:53 ` [PATCH 003 of 6] md: Remove 'experimental' classification from raid5 reshape NeilBrown
2006-09-29 4:24 ` Jeff Breidenbach
2006-10-02 8:07 ` David Greaves
2006-09-29 2:53 ` [PATCH 004 of 6] md: Use ffz instead of find_first_set to convert multiplier to shift NeilBrown
2006-09-29 2:53 ` [PATCH 005 of 6] md: Allow SET_BITMAP_FILE to work on 64bit kernel with 32bit userspace NeilBrown
2006-09-29 2:53 ` [PATCH 006 of 6] md: Add error reporting to superblock write failure NeilBrown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1060929025252.15187@suse.de \
--to=neilb@suse.de \
--cc=akpm@osdl.org \
--cc=evil@g-house.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).