summaryrefslogtreecommitdiffstats
path: root/mdadm.8.in
diff options
context:
space:
mode:
authorZhilong Liu <zlliu@suse.com>2018-02-02 07:10:50 +0100
committerJes Sorensen <jsorensen@fb.com>2018-03-08 20:30:53 +0100
commitb2a613ddd5f976680358141548197d534cbf8d53 (patch)
tree785766a1ef3d8c26a10c70f02b2880f06f2fe649 /mdadm.8.in
parentmdadm/clustermd_tests: delete meaningless commands in check (diff)
downloadmdadm-b2a613ddd5f976680358141548197d534cbf8d53.tar.xz
mdadm-b2a613ddd5f976680358141548197d534cbf8d53.zip
manpage: add prompt in --zero-superblock against clustered raid
Clustered raid would be damaged if calls --zero-superblock incorrectly, so add prompt in --zero-superblock chapter of manpage. Such as: cluster node1 has assembled cluster-md, but calls --zero-superblock in other cluster node. Signed-off-by: Zhilong Liu <zlliu@suse.com> Signed-off-by: Jes Sorensen <jsorensen@fb.com>
Diffstat (limited to 'mdadm.8.in')
-rw-r--r--mdadm.8.in4
1 files changed, 4 insertions, 0 deletions
diff --git a/mdadm.8.in b/mdadm.8.in
index f0fd1fce..e6befeb0 100644
--- a/mdadm.8.in
+++ b/mdadm.8.in
@@ -1691,6 +1691,10 @@ overwritten with zeros. With
the block where the superblock would be is overwritten even if it
doesn't appear to be valid.
+.B Note:
+Be careful to call \-\-zero\-superblock with clustered raid, make sure
+array isn't used or assembled in other cluster node before execute it.
+
.TP
.B \-\-kill\-subarray=
If the device is a container and the argument to \-\-kill\-subarray