e2fsck: allow deleting or zeroing shared blocks

[tools/e2fsprogs.git] / e2fsck / e2fsck.8.in

diff --git a/e2fsck/e2fsck.8.in b/e2fsck/e2fsck.8.in
index da9f618..d91c74d 100644 (file)
--- a/e2fsck/e2fsck.8.in
+++ b/e2fsck/e2fsck.8.in
@@ -198,6 +198,19 @@ separated, and may take an argument using the equals ('=') sign.  The
 following options are supported:
 .RS 1.2i
 .TP
+.BI clone= dup|zero
+Resolve files with shared blocks in pass 1D by giving each file a private
+copy of the blocks (dup);
+or replacing the shared blocks with private, zero-filled blocks (zero).
+The default is dup.
+.TP
+.BI shared= preserve|lost+found|delete
+Files with shared blocks discovered in pass 1D are cloned and then left
+in place (preserve);
+cloned and then disconnected from their parent directory,
+then reconnected to /lost+found in pass 3 (lost+found);
+or simply deleted (delete).  The default is preserve.
+.TP
 .BI ea_ver= extended_attribute_version
 Set the version of the extended attribute blocks which
 .B e2fsck
@@ -276,7 +289,7 @@ blocks anyway, then this option will have no effect. Note when using this
 option, if there is no free space to clone blocks, there is no prompt to
 delete files and instead the operation will fail.
 .IP
-Note that unshare_blocks requires the "-f" option to ensure that all passes
+Note that unshare_blocks implies the "-f" option to ensure that all passes
 are run. Additionally, if "-n" is also specified, e2fsck will simulate trying
 to allocate enough space to deduplicate. If this fails, the exit code will
 be non-zero.