From: james4765@verizon.net
To: linux-kernel@vger.kernel.org
Cc: akpm@osdl.org, mingo@redhat.com, james4765@verizon.net
Subject: [PATCH] md: Documentation/md.txt update
Date: Mon, 8 Nov 2004 22:20:30 -0600 [thread overview]
Message-ID: <20041109042030.11446.55146.88799@localhost.localdomain> (raw)
Update status of superblock formats and fix misspellings in Documentation/md.txt
Signed-off-by: James Nelson <james4765@gmail.com>
diff -urN --exclude='*~' linux-2.6.9-original/Documentation/md.txt linux-2.6.9/Documentation/md.txt
--- linux-2.6.9-original/Documentation/md.txt 2004-10-18 17:54:38.000000000 -0400
+++ linux-2.6.9/Documentation/md.txt 2004-11-08 23:06:51.131605977 -0500
@@ -55,13 +55,13 @@
------------------
The md driver can support a variety of different superblock formats.
-(It doesn't yet, but it can)
+Currently, it supports superblock formats "0.90.0" and the "md-1" format
+introduced in the 2.5 development series.
-The kernel does *NOT* autodetect which format superblock is being
-used. It must be told.
+The kernel will autodetect which format superblock is being used.
Superblock format '0' is treated differently to others for legacy
-reasons.
+reasons - it is the original superblock format.
General Rules - apply for all superblock formats
@@ -69,6 +69,7 @@
An array is 'created' by writing appropriate superblocks to all
devices.
+
It is 'assembled' by associating each of these devices with an
particular md virtual device. Once it is completely assembled, it can
be accessed.
@@ -76,10 +77,10 @@
An array should be created by a user-space tool. This will write
superblocks to all devices. It will usually mark the array as
'unclean', or with some devices missing so that the kernel md driver
-can create approrpriate redundancy (copying in raid1, parity
+can create appropriate redundancy (copying in raid1, parity
calculation in raid4/5).
-When an array is assembled, it is first initialised with the
+When an array is assembled, it is first initialized with the
SET_ARRAY_INFO ioctl. This contains, in particular, a major and minor
version number. The major version number selects which superblock
format is to be used. The minor number might be used to tune handling
@@ -101,15 +102,16 @@
Specific Rules that apply to format-0 super block arrays, and
- arrays with no superblock (non-persistant).
+ arrays with no superblock (non-persistent).
-------------------------------------------------------------
An array can be 'created' by describing the array (level, chunksize
etc) in a SET_ARRAY_INFO ioctl. This must has major_version==0 and
raid_disks != 0.
-Then uninitialised devices can be added with ADD_NEW_DISK. The
+
+Then uninitialized devices can be added with ADD_NEW_DISK. The
structure passed to ADD_NEW_DISK must specify the state of the device
and it's role in the array.
-One started with RUN_ARRAY, uninitialised spares can be added with
+One started with RUN_ARRAY, uninitialized spares can be added with
HOT_ADD_DISK.
next reply other threads:[~2004-11-09 4:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-09 4:20 james4765 [this message]
2004-11-09 5:05 ` Neil Brown
2004-11-09 22:47 ` Jim Nelson
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=20041109042030.11446.55146.88799@localhost.localdomain \
--to=james4765@verizon.net \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
/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
all inboxes | Powered by JetHome®