path: root/Documentation
diff options
authorDavid Sterba <>2017-05-31 13:49:08 +0200
committerDavid Sterba <>2017-06-26 17:08:15 +0200
commit921dc0a973c5850d90c143306fe3780cf21a6762 (patch)
treee55ddbfc76b5439bf62597a581d3954664d41e88 /Documentation
parentc1c987503412a8e98e40da2548c6b78888535641 (diff)
btrfs-progs: docs: update formatting of btrfs-rescue
Reported by a wiki user, that the 'zero-log' section indentaion is wrong. Signed-off-by: David Sterba <>
Diffstat (limited to 'Documentation')
1 files changed, 5 insertions, 5 deletions
diff --git a/Documentation/btrfs-rescue.asciidoc b/Documentation/btrfs-rescue.asciidoc
index 42aca645..a9b471fe 100644
--- a/Documentation/btrfs-rescue.asciidoc
+++ b/Documentation/btrfs-rescue.asciidoc
@@ -42,19 +42,19 @@ verbose mode.
*zero-log* <device>::
clear the filesystem log tree
This command will clear the filesystem log tree. This may fix a specific
set of problem when the filesystem mount fails due to the log replay. See below
for sample stacktraces that may show up in system log.
The common case where this happens has been fixed a long time ago,
so it is unlikely that you will see this particular problem, but the utility is
kept around.
NOTE: clearing the log may lead to loss of changes that were made since the
last transaction commit. This may be up to 30 seconds (default commit period)
or less if the commit was implied by other filesystem activity.
One can determine whether *zero-log* is needed according to the kernel
@@ -66,7 +66,7 @@ backtrace:
? btree_read_extent_buffer_pages+0x76/0xbc [btrfs]
? open_ctree+0xff6/0x132c [btrfs]
If the errors are like above, then *zero-log* should be used to clear
the log and the filesystem may be mounted normally again. The keywords to look
for are 'open_ctree' which says that it's during mount and function names