summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorKarel Zak2017-05-11 15:54:30 +0200
committerKarel Zak2017-05-11 15:54:30 +0200
commit5d217e6f158411dbd363a6ed5d3a7693ca87e847 (patch)
tree63fbe8ff4798e45afd4e22fb7b66354f2a15b020
parentfdisk: fix type dialog (diff)
downloadkernel-qcow2-util-linux-5d217e6f158411dbd363a6ed5d3a7693ca87e847.tar.gz
kernel-qcow2-util-linux-5d217e6f158411dbd363a6ed5d3a7693ca87e847.tar.xz
kernel-qcow2-util-linux-5d217e6f158411dbd363a6ed5d3a7693ca87e847.zip
wipefs: add note about no-act to the man page
Signed-off-by: Karel Zak <kzak@redhat.com>
-rw-r--r--misc-utils/wipefs.88
1 files changed, 6 insertions, 2 deletions
diff --git a/misc-utils/wipefs.8 b/misc-utils/wipefs.8
index 666c03c93..b7c7467fe 100644
--- a/misc-utils/wipefs.8
+++ b/misc-utils/wipefs.8
@@ -32,10 +32,14 @@ the device. The
command lists only the first offset where a magic string has been detected. The device
is not scanned for additional magic strings for the same filesystem. It is possible
that after a \fBwipefs -o \fIoffset\fR the same filesystem or partition
-table will still be visible because of another magic string on another offset.
+table will still be visible because of another magic string on another offset. The
+option \fB\-\-no\-act\fR is also affected by this behavior and only the first
+magic string for the filesystem is reported.
When option \fB-a\fR is used, all magic strings that are visible for libblkid are
-erased.
+erased. In this case the
+.B wipefs
+scans the device again after each modification (erase) until no magic string is found.
Note that by default
.B wipefs