|author||Dimitri John Ledkov <email@example.com>||2017-02-13 11:24:33 +0000|
|committer||Dimitri John Ledkov <firstname.lastname@example.org>||2017-02-13 11:24:33 +0000|
New upstream release Closes: #849353, #817806, #854915, #845473
Diffstat (limited to 'Documentation/btrfs-check.asciidoc')
1 files changed, 15 insertions, 1 deletions
diff --git a/Documentation/btrfs-check.asciidoc b/Documentation/btrfs-check.asciidoc
index abc9f0dc..633cbbf6 100644
@@ -20,7 +20,7 @@ by the option '--readonly'.
*btrfsck* is an alias of *btrfs check* command and is now deprecated.
-WARNING: Do not use '--repair' unless you are adviced to by a developer, an
+WARNING: Do not use '--repair' unless you are advised to by a developer, an
experienced user or accept the fact that 'fsck' cannot possibly fix all sorts
of damage that could happen to a filesystem because of software and hardware
@@ -78,6 +78,20 @@ respective superblock offset is within the device size
This can be used to use a different starting point if some of the primary
superblock is damaged.
+completely wipe all free space cache of given type
+For free space cache 'v1', the 'clear_cache' kernel mount option only rebuilds
+the free space cache for block groups that are modified while the filesystem is
+mounted with that option. Thus, using this option with 'v1' makes it possible
+to actually clear the entire free space cache.
+For free space cache 'v2', the 'clear_cache' kernel mount option does destroy
+the entire free space cache. This option with 'v2' provides an alternative
+method of clearing the free space cache that doesn't require mounting the