summaryrefslogtreecommitdiffstats
path: root/mdadm.8.in
diff options
context:
space:
mode:
authorDaniel Baumann <daniel.baumann@progress-linux.org>2023-03-13 16:55:45 +0000
committerDaniel Baumann <daniel.baumann@progress-linux.org>2023-03-13 16:55:45 +0000
commit1dd2d8ec5cee893c5ad432809b7d8351d361d297 (patch)
tree892a19ccfd8f11e5f4a0076f660e09c52d45ddf6 /mdadm.8.in
parentReleasing debian version 4.2+20230304-1. (diff)
downloadmdadm-1dd2d8ec5cee893c5ad432809b7d8351d361d297.tar.xz
mdadm-1dd2d8ec5cee893c5ad432809b7d8351d361d297.zip
Merging upstream version 4.2+20230313.
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'mdadm.8.in')
-rw-r--r--mdadm.8.in18
1 files changed, 17 insertions, 1 deletions
diff --git a/mdadm.8.in b/mdadm.8.in
index 64f71ed..6f0f6c1 100644
--- a/mdadm.8.in
+++ b/mdadm.8.in
@@ -838,6 +838,22 @@ array is resynced at creation. From Linux version 3.0,
can be used with that command to avoid the automatic resync.
.TP
+.BR \-\-write-zeroes
+When creating an array, send write zeroes requests to all the block
+devices. This should zero the data area on all disks such that the
+initial sync is not necessary and, if successfull, will behave
+as if
+.B \-\-assume\-clean
+was specified.
+.IP
+This is intended for use with devices that have hardware offload for
+zeroing, but despite this zeroing can still take several minutes for
+large disks. Thus a message is printed before and after zeroing and
+each disk is zeroed in parallel with the others.
+.IP
+This is only meaningful with --create.
+
+.TP
.BR \-\-backup\-file=
This is needed when
.B \-\-grow
@@ -1370,7 +1386,7 @@ and
.B layout\-alternate
options are for RAID0 arrays with non-uniform devices size that were in
use before Linux 5.4. If the array was being used with Linux 3.13 or
-earlier, then to assemble the array on a new kernel,
+earlier, then to assemble the array on a new kernel,
.B \-\-update=layout\-original
must be given. If the array was created and used with a kernel from Linux 3.14 to
Linux 5.3, then