Michael Evan: Document validity of --assume-clean when all devices are zeroed.

[Martin F. Krafft]

Module: mdadm
Branch: upstream
Commit: 6acad4811b06335a2602fa1eeaec3a8f47f96591
URL:    http://git.debian.org/?p=pkg-mdadm/mdadm.git;a=commit;h=6acad4811b06335a2602fa1eeaec3a8f47f96591

Author: Michael Evan <mjevans1983 at gmail.com>
Date:   Wed Dec  9 21:52:18 2009 -0800

Document validity of --assume-clean when all devices are zeroed.

>>
>> When I assemble an array I tend to have checked the devices before
>> hand; it would not be difficult to make the final pass a zeroing pass
>> if I knew I could vastly speed up post-assembly performance.  As I
>> stated, it's merely a lack of clarity in the documentation.
>
> If you would like to create a patch against the man page, I would be happy to
> accept it.
>
> NeilBrown


Signed-off-by: NeilBrown <neilb at suse.de>

---

 mdadm.8 |    6 ++++++
 1 files changed, 6 insertions(+), 0 deletions(-)

diff --git a/mdadm.8 b/mdadm.8
index f8f240a..29e098b 100644
--- a/mdadm.8
+++ b/mdadm.8
@@ -648,6 +648,12 @@ data will be affected unless you actually write to the array.  It can
 also be used when creating a RAID1 or RAID10 if you want to avoid the
 initial resync, however this practice \(em while normally safe \(em is not
 recommended.  Use this only if you really know what you are doing.
+.IP
+When the devices that will be part of a new array were filled
+with zeros before creation the operator knows the array is
+actually clean. If that is the case, such as after running
+badblocks, this argument can be used to tell mdadm the
+facts the operator knows.
 
 .TP
 .BR \-\-backup\-file=