179 lines
6.5 KiB
Diff
179 lines
6.5 KiB
Diff
--- mdadm-3.2.2/mdadm.8.in.man 2011-06-17 01:15:50.000000000 -0400
|
|
+++ mdadm-3.2.2/mdadm.8.in 2011-07-14 20:18:49.240997107 -0400
|
|
@@ -336,7 +336,7 @@ It can easily be moved between hosts wit
|
|
recovery operation can be checkpointed and restarted. The different
|
|
sub-versions store the superblock at different locations on the
|
|
device, either at the end (for 1.0), at the start (for 1.1) or 4K from
|
|
-the start (for 1.2). "1" is equivalent to "1.0".
|
|
+the start (for 1.2). "1" is equivalent to "1.2".
|
|
'if '{DEFAULT_METADATA}'1.2' "default" is equivalent to "1.2".
|
|
.IP ddf
|
|
Use the "Industry Standard" DDF (Disk Data Format) format defined by
|
|
@@ -706,7 +706,7 @@ facts the operator knows.
|
|
When an array is resized to a larger size with
|
|
.B "\-\-grow \-\-size="
|
|
the new space is normally resynced in that same way that the whole
|
|
-array is resynced at creation. From Linux version 2.6.40,
|
|
+array is resynced at creation. From Linux version 3.0,
|
|
.B \-\-assume\-clean
|
|
can be used with that command to avoid the automatic resync.
|
|
|
|
@@ -811,6 +811,11 @@ number, and there is no entry in /dev fo
|
|
non-standard name. Names that are not in 'standard' format are only
|
|
allowed in "/dev/md/".
|
|
|
|
+This is meaningful with
|
|
+.B \-\-create
|
|
+or
|
|
+.BR \-\-build .
|
|
+
|
|
.ig XX
|
|
.\".TP
|
|
.\".BR \-\-symlink = no
|
|
@@ -835,6 +840,28 @@ allowed in "/dev/md/".
|
|
.\"
|
|
.XX
|
|
|
|
+.TP
|
|
+.BR \-a ", " "\-\-add"
|
|
+This option can be used in Grow mode in two cases.
|
|
+
|
|
+If the target array is a Linear array, then
|
|
+.B \-\-add
|
|
+can be used to add one or more devices to the array. They
|
|
+are simply catenated on to the end of the array. Once added, the
|
|
+devices cannot be removed.
|
|
+
|
|
+If the
|
|
+.B \-\-raid\-disks
|
|
+option is being used to increase the number of devices in an array,
|
|
+then
|
|
+.B \-\-add
|
|
+can be used to add some extra devices to be included in the array.
|
|
+In most cases this is not needed as the extra devices can be added as
|
|
+spares first, and then the number of raid-disks can be changed.
|
|
+However for RAID0, it is not possible to add spares. So to increase
|
|
+the number of devices in a RAID0, it is necessary to set the new
|
|
+number of devices, and to add the new devices, in the same command.
|
|
+
|
|
.SH For assemble:
|
|
|
|
.TP
|
|
@@ -912,28 +939,6 @@ not as reliable as you would like.
|
|
See this option under Create and Build options.
|
|
|
|
.TP
|
|
-.BR \-a ", " "\-\-add"
|
|
-This option can be used in Grow mode in two cases.
|
|
-
|
|
-If the target array is a Linear array, then
|
|
-.B \-\-add
|
|
-can be used to add one or more devices to the array. They
|
|
-are simply catenated on to the end of the array. Once added, the
|
|
-devices cannot be removed.
|
|
-
|
|
-If the
|
|
-.B \-\-raid\-disks
|
|
-option is being used to increase the number of devices in an array,
|
|
-then
|
|
-.B \-\-add
|
|
-can be used to add some extra devices to be included in the array.
|
|
-In most cases this is not needed as the extra devices can be added as
|
|
-spares first, and then the number of raid-disks can be changed.
|
|
-However for RAID0, it is not possible to add spares. So to increase
|
|
-the number of devices in a RAID0, it is necessary to set the new
|
|
-number of devices, and to add the new devices, in the same command.
|
|
-
|
|
-.TP
|
|
.BR \-b ", " \-\-bitmap=
|
|
Specify the bitmap file that was given when the array was created. If
|
|
an array has an
|
|
@@ -1491,7 +1496,7 @@ the first device given is the md device.
|
|
In the second usage example, all devices listed are treated as md
|
|
devices and assembly is attempted.
|
|
In the third (where no devices are listed) all md devices that are
|
|
-listed in the configuration file are assembled. If not arrays are
|
|
+listed in the configuration file are assembled. If no arrays are
|
|
described by the configuration file, then any arrays that
|
|
can be found on unused devices will be assembled.
|
|
|
|
@@ -1600,7 +1605,7 @@ and no devices are listed,
|
|
will first attempt to assemble all the arrays listed in the config
|
|
file.
|
|
|
|
-In no array at listed in the config (other than those marked
|
|
+If no arrays are listed in the config (other than those marked
|
|
.BR <ignore> )
|
|
it will look through the available devices for possible arrays and
|
|
will try to assemble anything that it finds. Arrays which are tagged
|
|
@@ -2200,11 +2205,11 @@ change the "size" attribute for RAID1, R
|
|
.IP \(bu 4
|
|
increase or decrease the "raid\-devices" attribute of RAID0, RAID1, RAID4,
|
|
RAID5, and RAID6.
|
|
-.IP \bu 4
|
|
+.IP \(bu 4
|
|
change the chunk-size and layout of RAID0, RAID4, RAID5 and RAID6.
|
|
-.IP \bu 4
|
|
+.IP \(bu 4
|
|
convert between RAID1 and RAID5, between RAID5 and RAID6, between
|
|
-RAID0, RAID5, and RAID5, and between RAID0 and RAID10 (in the near-2 mode).
|
|
+RAID0, RAID4, and RAID5, and between RAID0 and RAID10 (in the near-2 mode).
|
|
.IP \(bu 4
|
|
add a write-intent bitmap to any array which supports these bitmaps, or
|
|
remove a write-intent bitmap from such an array.
|
|
@@ -2250,7 +2255,7 @@ space to start being used. If the size
|
|
are synchronised.
|
|
|
|
Note that when an array changes size, any filesystem that may be
|
|
-stored in the array will not automatically grow for shrink to use or
|
|
+stored in the array will not automatically grow or shrink to use or
|
|
vacate the space. The
|
|
filesystem will need to be explicitly told to use the extra space
|
|
after growing, or to reduce its size
|
|
@@ -2259,7 +2264,7 @@ to shrinking the array.
|
|
|
|
Also the size of an array cannot be changed while it has an active
|
|
bitmap. If an array has a bitmap, it must be removed before the size
|
|
-can be changed. Once the change it complete a new bitmap can be created.
|
|
+can be changed. Once the change is complete a new bitmap can be created.
|
|
|
|
.SS RAID\-DEVICES CHANGES
|
|
|
|
@@ -2435,8 +2440,8 @@ must match one of the names or patterns
|
|
line.
|
|
|
|
.IP +
|
|
-Does the device have a valid md superblock. If a specific metadata
|
|
-version is request with
|
|
+Does the device have a valid md superblock? If a specific metadata
|
|
+version is requested with
|
|
.B \-\-metadata
|
|
or
|
|
.B \-e
|
|
@@ -2467,6 +2472,7 @@ is not able to positively identify the a
|
|
current host, the device will be rejected.
|
|
..
|
|
|
|
+.PP
|
|
.I mdadm
|
|
keeps a list of arrays that it has partially assembled in
|
|
.B /var/run/mdadm/map
|
|
@@ -2639,7 +2645,7 @@ can be started.
|
|
Any devices which are components of /dev/md4 will be marked as faulty
|
|
and then remove from the array.
|
|
|
|
-.B " mdadm --grow /dev/md4 --level=6 --backup-file=/root/backup-md4
|
|
+.B " mdadm --grow /dev/md4 --level=6 --backup-file=/root/backup-md4"
|
|
.br
|
|
The array
|
|
.B /dev/md4
|
|
@@ -2787,7 +2793,7 @@ configuration file at all.
|
|
For further information on mdadm usage, MD and the various levels of
|
|
RAID, see:
|
|
.IP
|
|
-.B http://linux\-raid.osdl.org/
|
|
+.B http://raid.wiki.kernel.org/
|
|
.PP
|
|
(based upon Jakob \(/Ostergaard's Software\-RAID.HOWTO)
|
|
.\".PP
|