From: Neil Brown <neilb@suse.de>
Date: Tue, 7 Jun 2005 23:25:48 +0000 (+0000)
Subject: Document --size=max option for --grow
X-Git-Tag: mdadm-1.12.0~22
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=be0b132b458b481c147e495fdf8c6eae66ce3a97;p=thirdparty%2Fmdadm.git

Document --size=max option for --grow

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

diff --git a/ChangeLog b/ChangeLog
index 25e0fec2..c78a97e7 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,6 +1,8 @@
 Changes Prior to 1.12.0 release
     -   Don't use 'lstat' to check for blockdevices, use stat.
     -   Get size calculation right when in Create when BLKGESIZE64 not available
+    -   Document --size=max option for --grow
+	
 Changes Prior to 1.11.0 release
     -   Fix embarassing bug which causes --add to always fail.
 
diff --git a/mdadm.8 b/mdadm.8
index 3e1c64ad..1a346909 100644
--- a/mdadm.8
+++ b/mdadm.8
@@ -344,6 +344,9 @@ for RAID level 1/4/5/6. If the array was created with a size smaller
 than the currently active drives, the extra space can be accessed
 using
 .BR --grow .
+The size can be given as
+.B max
+which means to choose the largest size that fits all on all current drives.
 
 .TP
 .BR --assume-clean