From: Nikolay Borisov <nborisov@suse.com>
To: Su Yue <suy.fnst@cn.fujitsu.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: Add more details while checking tree block
Date: Fri, 22 Jun 2018 14:48:30 +0300 [thread overview]
Message-ID: <7b34f539-ef57-ecb3-37c8-7b3759874249@suse.com> (raw)
In-Reply-To: <20180622015215.31812-1-suy.fnst@cn.fujitsu.com>
On 22.06.2018 04:52, Su Yue wrote:
> For easier debug, print eb->start if level is invalid.
> Also make print clear if bytenr found is not expected.
>
> Signed-off-by: Su Yue <suy.fnst@cn.fujitsu.com>
> ---
> fs/btrfs/disk-io.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/fs/btrfs/disk-io.c b/fs/btrfs/disk-io.c
> index c3504b4d281b..a90dab84f41b 100644
> --- a/fs/btrfs/disk-io.c
> +++ b/fs/btrfs/disk-io.c
> @@ -615,8 +615,8 @@ static int btree_readpage_end_io_hook(struct btrfs_io_bio *io_bio,
>
> found_start = btrfs_header_bytenr(eb);
> if (found_start != eb->start) {
> - btrfs_err_rl(fs_info, "bad tree block start %llu %llu",
> - found_start, eb->start);
> + btrfs_err_rl(fs_info, "bad tree block start want %llu have %llu",
nit: I'd rather have the want/have in brackets (want %llu have% llu)
> + eb->start, found_start);
> ret = -EIO;
> goto err;
> }
> @@ -628,8 +628,8 @@ static int btree_readpage_end_io_hook(struct btrfs_io_bio *io_bio,
> }
> found_level = btrfs_header_level(eb);
> if (found_level >= BTRFS_MAX_LEVEL) {
> - btrfs_err(fs_info, "bad tree block level %d",
> - (int)btrfs_header_level(eb));
> + btrfs_err(fs_info, "bad tree block level %d on %llu",
> + (int)btrfs_header_level(eb), eb->start);
> ret = -EIO;
> goto err;
> }
>
next prev parent reply other threads:[~2018-06-22 11:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-22 1:52 [PATCH] btrfs: Add more details while checking tree block Su Yue
2018-06-22 11:44 ` David Sterba
2018-06-22 11:48 ` Nikolay Borisov [this message]
[not found] ` <CABnRu560BS0NDcuEEfexR-vkqTOMpUkAB0bWYSM8G2957yTm6w@mail.gmail.com>
2018-06-22 15:17 ` Fwd: " Su Yue
2018-06-22 15:26 ` Hans van Kranenburg
2018-06-22 15:40 ` Hugo Mills
2018-06-22 16:15 ` Su Yue
2018-06-22 16:17 ` Su Yue
2018-06-22 16:25 ` Nikolay Borisov
2018-06-22 16:29 ` Hans van Kranenburg
2018-06-22 18:26 ` Noah Massey
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=7b34f539-ef57-ecb3-37c8-7b3759874249@suse.com \
--to=nborisov@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=suy.fnst@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