* [PATCH] btrfs-progs: Doc: Fix asciidoc grammar of btrfs-rescue
@ 2017-08-21 6:57 Qu Wenruo
2017-08-21 17:05 ` David Sterba
0 siblings, 1 reply; 2+ messages in thread
From: Qu Wenruo @ 2017-08-21 6:57 UTC (permalink / raw)
To: linux-btrfs; +Cc: dsterba
Code block of kernel backtrace lacks leading change line, causing the
following man page result:
------
One can determine whether zero-log is needed according to the
kernel backtrace:
? replay_one_dir_item+0xb5/0xb5 [btrfs]
? walk_log_tree+0x9c/0x19d [btrfs]
? btrfs_read_fs_root_no_radix+0x169/0x1a1 [btrfs]
? btrfs_recover_log_trees+0x195/0x29c [btrfs]
? replay_one_dir_item+0xb5/0xb5 [btrfs]
? 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
------
Not only "+" is rendered as is, but also wrong indent.
Fix it by adding change line before code block.
Signed-off-by: Qu Wenruo <quwenruo.btrfs@gmx.com>
---
Documentation/btrfs-rescue.asciidoc | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/btrfs-rescue.asciidoc b/Documentation/btrfs-rescue.asciidoc
index a9b471fe..24b619c6 100644
--- a/Documentation/btrfs-rescue.asciidoc
+++ b/Documentation/btrfs-rescue.asciidoc
@@ -57,6 +57,7 @@ or less if the commit was implied by other filesystem activity.
+
One can determine whether *zero-log* is needed according to the kernel
backtrace:
++
----
? replay_one_dir_item+0xb5/0xb5 [btrfs]
? walk_log_tree+0x9c/0x19d [btrfs]
--
2.14.1
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH] btrfs-progs: Doc: Fix asciidoc grammar of btrfs-rescue
2017-08-21 6:57 [PATCH] btrfs-progs: Doc: Fix asciidoc grammar of btrfs-rescue Qu Wenruo
@ 2017-08-21 17:05 ` David Sterba
0 siblings, 0 replies; 2+ messages in thread
From: David Sterba @ 2017-08-21 17:05 UTC (permalink / raw)
To: Qu Wenruo; +Cc: linux-btrfs, dsterba
On Mon, Aug 21, 2017 at 03:57:04PM +0900, Qu Wenruo wrote:
> Code block of kernel backtrace lacks leading change line, causing the
> following man page result:
> ------
> One can determine whether zero-log is needed according to the
> kernel backtrace:
>
> ? replay_one_dir_item+0xb5/0xb5 [btrfs]
> ? walk_log_tree+0x9c/0x19d [btrfs]
> ? btrfs_read_fs_root_no_radix+0x169/0x1a1 [btrfs]
> ? btrfs_recover_log_trees+0x195/0x29c [btrfs]
> ? replay_one_dir_item+0xb5/0xb5 [btrfs]
> ? 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
> ------
>
> Not only "+" is rendered as is, but also wrong indent.
>
> Fix it by adding change line before code block.
>
> Signed-off-by: Qu Wenruo <quwenruo.btrfs@gmx.com>
Applied, thanks.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2017-08-21 17:07 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-08-21 6:57 [PATCH] btrfs-progs: Doc: Fix asciidoc grammar of btrfs-rescue Qu Wenruo
2017-08-21 17:05 ` David Sterba
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.