same as
.BR \-\-fail .
+.TP
+.BR \-\-write\-mostly
+Subsequent devices that are added or re-added will have the 'write-mostly'
+flag set. This is only valid for RAID! and means that the 'md' driver
+will avoid reading from these devices if possible.
+.TP
+.BR \-\-readwrite
+Subsequent devices that are added or re-added will have the 'write-mostly'
+flag cleared.
+
+
.P
Each of these options require that the first device listed is the array
to be acted upon, and the remainder are component devices to be added,
.TP
.BR \-\-wait\-clean
-For each md device given, wait for the array to be marked clean before
-returning. For native arrays this returns immediately as the kernel
-handles dirty-clean transistions at shutdown.
+For each md device given, arrange for the array to be marked clean as
+soon as possible. Also, quiesce resync so that the monitor for external
+metadata arrays (mdmon) has an opportunity to checkpoint the resync
+position.
+.I mdadm
+will return with success if the array uses external metadata and we
+successfully waited. For native arrays this returns immediately as the
+kernel handles both dirty-clean transitions and resync checkpointing in
+the kernel at shutdown. No action is taken if safe-mode handling is
+disabled.
.SH For Incremental Assembly mode:
.TP
.SH SEE ALSO
For further information on mdadm usage, MD and the various levels of
RAID, see:
-
.IP
-.UR http://linux-raid.osdl.org/
-http://linux\-raid.osdl.org/
-.UE
+.B http://linux\-raid.osdl.org/
.PP
(based upon Jakob \(/Ostergaard's Software\-RAID.HOWTO)
.\".PP
.I mdadm
should always be available from
.IP
-.UR http://www.kernel.org/pub/linux/utils/raid/mdadm/
-http://www.kernel.org/pub/linux/utils/raid/mdadm/
-.UE
+.B http://www.kernel.org/pub/linux/utils/raid/mdadm/
+.PP
+Related man pages:
.PP
.IR mdadm.conf (5),
.IR md (4).