| Message ID | 20170821065704.12119-1-quwenruo.btrfs@gmx.com (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
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. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
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]
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(+)