Skip to contentSkip to conversation

btrfs-progs: doc: fix the out-of-date contents on btrfs-progs support on free space cache tree

PATCH In review Qu Wenruo 3 participants 3 messages Jul 14, 2021 – Jul 22, 2021

Subsystems (2)
lore
Share & tools
lore

Qu Wenruo

author
#0 lore raw

PATCH 1/1 btrfs-progs: doc: fix the out-of-date contents on btrfs-progs support on free space cache tree

Since v4.19, btrfs-progs has full write support to free space tree, the out-of-date warning in btrfs(5) has already confused some end user.

Update the content to avoid further confusion.

---
 Documentation/btrfs-man5.asciidoc | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)
Documentation/btrfs-man5.asciidoc +4 -4
index 806ac786c3c4..813a9fb08d6e 100644
@@ -385,10 +385,10 @@ implementation, which adds a new B-tree called the free space tree, addresses
 this issue. Once enabled, the 'v2' space cache will always be used and cannot
 be disabled unless it is cleared. Use 'clear_cache,space_cache=v1' or
 'clear_cache,nospace_cache' to do so. If 'v2' is enabled, kernels without 'v2'
-support will only be able to mount the filesystem in read-only mode. The
-`btrfs`(8) command currently only has read-only support for 'v2'. A read-write
-command may be run on a 'v2' filesystem by clearing the cache, running the
-command, and then remounting with 'space_cache=v2'.
+support will only be able to mount the filesystem in read-only mode.
++
+The `btrfs-check`(8) and `mkfs.btrfs`(8) commands have full 'v2' free space
+cache support since v4.19.
 +
 If a version is not explicitly specified, the default implementation will be
 chosen, which is 'v1'.
Signature · 1 line
2.32.0