From: Marc MERLIN <marc@merlins.org>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 2/2] btrfs-progs: Add explain on btrfs-zero-log.
Date: Thu, 10 Apr 2014 23:11:38 -0700 [thread overview]
Message-ID: <20140411061138.GE7322@merlins.org> (raw)
In-Reply-To: <1397184233-18535-2-git-send-email-quwenruo@cn.fujitsu.com>
On Fri, Apr 11, 2014 at 10:43:53AM +0800, Qu Wenruo wrote:
> Add more explain on btrfs-zero-log about when to use it.
>
> Cc: Marc MERLIN <marc@merlins.org>
> Signed-off-by: Qu Wenruo <quwenruo@cn.fujitsu.com>
Reviewed-by: Marc MERLIN <marc@merlins.org>
Looks good, thank you.
Marc
> ---
> Documentation/btrfs-zero-log.txt | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
>
> diff --git a/Documentation/btrfs-zero-log.txt b/Documentation/btrfs-zero-log.txt
> index e3041fa..a8e4dd3 100644
> --- a/Documentation/btrfs-zero-log.txt
> +++ b/Documentation/btrfs-zero-log.txt
> @@ -17,6 +17,24 @@ allow you to mount the filesystem again.
> The common case where this happens has been fixed a long time ago,
> so it is unlikely that you will see this particular problem.
>
> +One can determine whether 'btrfs-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 'btrfs-zero-log' should be used to clear
> +the log and the filesystem may be mounted normally again.
> +
> +NOTE: If you use btrfs as the root filesystem, you may want to include
> +'btrfs-zero-log' into initramdisk if the log problems hits you often.
> +
> EXIT STATUS
> -----------
> 'btrfs-zero-log' will return 0 if no error happened.
> --
> 1.9.2
>
> --
> 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
>
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/
next prev parent reply other threads:[~2014-04-11 6:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-11 2:43 [PATCH 1/2] btrfs-progs: Add device management related paragraph Qu Wenruo
2014-04-11 2:43 ` [PATCH 2/2] btrfs-progs: Add explain on btrfs-zero-log Qu Wenruo
2014-04-11 6:11 ` Marc MERLIN [this message]
2014-04-11 6:10 ` [PATCH 1/2] btrfs-progs: Add device management related paragraph Marc MERLIN
2014-04-11 9:08 ` Qu Wenruo
2014-04-11 17:36 ` David Sterba
2014-04-11 17:52 ` Marc MERLIN
2014-04-14 1:16 ` Qu Wenruo
2014-04-14 1:45 ` wiki vs man pages Marc MERLIN
2014-04-14 2:00 ` Qu Wenruo
2014-04-11 9:16 ` [PATCH 1/2] btrfs-progs: Add device management related paragraph Liu Bo
2014-04-11 17:34 ` David Sterba
2014-04-14 1:09 ` Qu Wenruo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140411061138.GE7322@merlins.org \
--to=marc@merlins.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo@cn.fujitsu.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).