summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorNeil Brown <neilb@suse.de>2007-02-22 14:59:22 +1100
committerNeil Brown <neilb@suse.de>2007-02-22 14:59:22 +1100
commit00be0b12d234b2dc3c78ebc8dc342092061091ec (patch)
tree96b3eb3d027d26277e9481e9c5442dbd7735ad2d
parent48327135d67609488c2535482f6f24874c94412a (diff)
downloadmdadm-00be0b12d234b2dc3c78ebc8dc342092061091ec.tar.gz
mdadm-00be0b12d234b2dc3c78ebc8dc342092061091ec.tar.xz
mdadm-00be0b12d234b2dc3c78ebc8dc342092061091ec.zip
Fixed old documentation in --grow --help
-rw-r--r--ChangeLog1
-rw-r--r--ReadMe.c13
-rw-r--r--mdadm.87
3 files changed, 14 insertions, 7 deletions
diff --git a/ChangeLog b/ChangeLog
index 98736df..79d66e5 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -4,6 +4,7 @@ Changes Prior to this release
- Fully support --grow for raid6. If a reshape crashed during the
critical period, mdadm wouldn't restore the Q information
properly.
+ - Update documentation for --grow.
Changes Prior to 2.6 release
- Fixed UUID printing in "--detail --brief" for version1 metadata.
diff --git a/ReadMe.c b/ReadMe.c
index 4e0a949..6ffb0f4 100644
--- a/ReadMe.c
+++ b/ReadMe.c
@@ -504,16 +504,21 @@ char Help_grow[] =
"\n"
"This usage causes mdadm to attempt to reconfigure a running array.\n"
"This is only possibly if the kernel being used supports a particular\n"
-"reconfiguration. This version only supports changing the number of\n"
-"devices in a RAID1, and changing the active size of all devices in\n"
-"a RAID1/4/5/6.\n"
+"reconfiguration. This version supports changing the number of\n"
+"devices in a RAID1/5/6, changing the active size of all devices in\n"
+"a RAID1/4/5/6, adding or removing a write-intent bitmap, and changing\n"
+"the error mode for a 'FAULTY' array.\n"
"\n"
"Options that are valid with the grow (-G --grow) mode are:\n"
+" --level= -l : Tell mdadm what level the array is so that it can\n"
+" : interpret '--layout' properly.\n"
+" --layout= -p : For a FAULTY array, set/change the error mode.\n"
" --size= -z : Change the active size of devices in an array.\n"
" : This is useful if all devices have been replaced\n"
" : with larger devices.\n"
-" --raid-disks= -n : Change the number of active devices in a RAID1\n"
+" --raid-disks= -n : Change the number of active devices in an array.\n"
" : array.\n"
+" --bitmap= -b : Add or remove a write-intent bitmap.\n"
;
char Help_incr[] =
diff --git a/mdadm.8 b/mdadm.8
index 2270c7d..f0a609c 100644
--- a/mdadm.8
+++ b/mdadm.8
@@ -129,7 +129,7 @@ missing, spare, or failed drives, so there is nothing to monitor.
Grow (or shrink) an array, or otherwise reshape it in some way.
Currently supported growth options including changing the active size
of component devices in RAID level 1/4/5/6 and changing the number of
-active devices in RAID1.
+active devices in RAID1/5/6.
.TP
.B "Incremental Assembly"
@@ -346,7 +346,8 @@ multipath, raid0 and raid1. It is never allowed for raid4 or raid5.
.br
This number can only be changed using
.B --grow
-for RAID1 arrays, and only on kernels which provide necessary support.
+for RAID1, RAID5 and RAID6 arrays, and only on kernels which provide
+necessary support.
.TP
.BR -x ", " --spare-devices=
@@ -1660,7 +1661,7 @@ Currently the only support available is to
change the "size" attribute
for RAID1, RAID5 and RAID6.
.IP \(bu 4
-increase the "raid-disks" attribute of RAID1 and RAID5.
+increase the "raid-disks" attribute of RAID1, RAID5, and RAID6.
.IP \(bu 4
add a write-intent bitmap to any array which support these bitmaps, or
remove a write-intent bitmap from such an array.