Lots of little manpage updates.

Signed-off-by: Neil Brown <neilb@cse.unsw.edu.au>

1 files changed, 30 insertions, 7 deletions

diff --git a/md.4 b/md.4
index b66fa1af..ae619e53 100644
--- a/md.4
+++ b/md.4
@@ -240,10 +240,10 @@ in a MULTIPATH md array.  However there are multiple access points
 (paths) to this device, and one of these paths might fail, so there
 are some similarities.
 
-A MULTIPATH array is composed of a number of logical different
+A MULTIPATH array is composed of a number of logically different
 devices, often fibre channel interfaces, that all refer the the same
 real device. If one of these interfaces fails (e.g. due to cable
-problems), the multipath driver to attempt to redirect requests to
+problems), the multipath driver will attempt to redirect requests to
 another interface. 
 
 .SS FAULTY
@@ -253,7 +253,7 @@ superblock, so the md array created provides direct access to all of
 the data in the component device.
 
 The FAULTY module may be requested to simulate faults to allow testing
-of other md levels or of filesystem.  Faults can be chosen to trigger
+of other md levels or of filesystems.  Faults can be chosen to trigger
 on read requests or write requests, and can be transient (a subsequent
 read/write at the address will probably succeed) or persistant
 (subsequent read/write of the same address will fail).  Further, read
@@ -261,9 +261,9 @@ faults can be "fixable" meaning that they persist until a write
 request at the same address.
 
 Fault types can be requested with a period.  In this case the fault
-will recur repeatedly after the given number of request of the
-relevant time.  For example if persistent read faults have a period of
-100, then ever 100th read request would generate a fault, and the
+will recur repeatedly after the given number of requests of the
+relevant type.  For example if persistent read faults have a period of
+100, then every 100th read request would generate a fault, and the
 faulty sector would be recorded so that subsequent reads on that
 sector would also fail.
 
@@ -271,7 +271,7 @@ There is a limit to the number of faulty sectors that are remembered.
 Faults generated after this limit is exhausted are treated as
 transient.
 
-It list of faulty sectors can be flushed, and the active list of
+The list of faulty sectors can be flushed, and the active list of
 failure modes can be cleared.
 
 .SS UNCLEAN SHUTDOWN
@@ -393,13 +393,36 @@ an MD array, and if any full arrays are found, they are started.  This
 kernel paramenter disables this behaviour.
 
 .TP
+.B raid=partitionable
+.TP
+.B raid=part
+These are available in 2.6 and later kernels only.  They indicate that
+autodetected MD arrays should be created as partitionable arrays, with
+a different major device number to the original non-partitionable md
+arrays.  The device number is listed as
+.I mdp
+in
+.IR /proc/devices .
+
+
+.TP
 .BI md= n , dev , dev ,...
+.TP
+.BI md=d n , dev , dev ,...
 This tells the md driver to assemble
 .B /dev/md n
 from the listed devices.  It is only necessary to start the device
 holding the root filesystem this way.  Other arrays are best started
 once the system is booted.
 
+In 2.6 kernels, the
+.B d
+immediately after the
+.B =
+indicates that a partitionable device (e.g.
+.BR /dev/md/d0 )
+should be created rather than the original non-partitionable device.
+
 .TP
 .BI md= n , l , c , i , dev...
 This tells the md driver to assemble a legacy RAID0 or LINEAR array