Martchus
/
mdadm
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

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@suse.de>
This commit is contained in:
Michael Evan 2009-12-09 21:52:18 -08:00 committed by NeilBrown
parent 8409bc51e8
commit 6acad4811b
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
mdadm.8
View File

@ -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=