array_try_spare(): missing map_unlock()

[thirdparty/mdadm.git] / md.4

diff --git a/md.4 b/md.4
index 5e796393ed621f080628ab1f977968e3353cfe18..99faad1ac50c48a3592b7ac27e5c1a8d20070923 100644 (file)
--- a/md.4
+++ b/md.4
@@ -120,7 +120,7 @@ a MULTIPATH array with no superblock makes sense.
 RAID1
 In some configurations it might be desired to create a raid1
 configuration that does not use a superblock, and to maintain the state of
-the array elsewhere.  While not encouraged for general us, it does
+the array elsewhere.  While not encouraged for general use, it does
 have special-purpose uses and is supported.
 
 .SS ARRAYS WITH EXTERNAL METADATA
@@ -128,7 +128,7 @@ have special-purpose uses and is supported.
 From release 2.6.28, the
 .I md
 driver supports arrays with externally managed metadata.  That is,
-the metadata is not managed by the kernel by rather by a user-space
+the metadata is not managed by the kernel but rather by a user-space
 program which is external to the kernel.  This allows support for a
 variety of metadata formats without cluttering the kernel with lots of
 details.
@@ -136,7 +136,7 @@ details.
 .I md
 is able to communicate with the user-space program through various
 sysfs attributes so that it can make appropriate changes to the
-metadata \- for example to make a device as faulty.  When necessary,
+metadata \- for example to mark a device as faulty.  When necessary,
 .I md
 will wait for the program to acknowledge the event by writing to a
 sysfs attribute.
@@ -215,7 +215,7 @@ spindle. In theory, having an N-disk RAID1 will allow N sequential
 threads to read from all disks.
 
 Individual devices in a RAID1 can be marked as "write-mostly".
-This drives are excluded from the normal read balancing and will only
+These drives are excluded from the normal read balancing and will only
 be read from when there is no other option.  This can be useful for
 devices connected over a slow link.
 
@@ -468,7 +468,7 @@ scrub starts and is incremented whenever a sector is
 found that is a mismatch.
 .I md
 normally works in units much larger than a single sector and when it
-finds a mismatch, it does not determin exactly how many actual sectors were
+finds a mismatch, it does not determine exactly how many actual sectors were
 affected but simply adds the number of sectors in the IO unit that was
 used.  So a value of 128 could simply mean that a single 64KB check
 found an error (128 x 512bytes = 64KB).
@@ -661,7 +661,7 @@ to this file will cause the system-wide setting to have effect.
 This is the partner of
 .B md/sync_speed_min
 and overrides
-.B /proc/sys/dev/raid/spool_limit_max
+.B /proc/sys/dev/raid/speed_limit_max
 described below.
 
 .TP