From 4305d024938113df5d73021a09eb2a991f54ca2f Mon Sep 17 00:00:00 2001 From: Dimitri John Ledkov Date: Mon, 13 Feb 2017 11:24:33 +0000 Subject: New upstream release Closes: #849353, #817806, #854915, #845473 --- Documentation/btrfs-check.asciidoc | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) (limited to 'Documentation/btrfs-check.asciidoc') diff --git a/Documentation/btrfs-check.asciidoc b/Documentation/btrfs-check.asciidoc index abc9f0dc..633cbbf6 100644 --- a/Documentation/btrfs-check.asciidoc +++ b/Documentation/btrfs-check.asciidoc @@ -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 bugs. @@ -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. +--clear-space-cache v1|v2:: +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 +filesystem. + + DANGEROUS OPTIONS ----------------- -- cgit v1.2.3