public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Nikolay Borisov <nborisov@suse.com>
To: Su Yue <Damenly_Su@gmx.com>,
	Hans van Kranenburg <hans.van.kranenburg@mendix.com>
Cc: 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 19:25:00 +0300	[thread overview]
Message-ID: <1d838113-c2be-c80a-4238-8d2c52b3663c@suse.com> (raw)
In-Reply-To: <trinity-79615ff6-1782-43b2-b564-19a911272004-1529684276139@3c-app-mailcom-bs09>



On 22.06.2018 19:17, Su Yue wrote:
> 
> 
> 
>> Sent: Friday, June 22, 2018 at 11:26 PM
>> From: "Hans van Kranenburg" <hans.van.kranenburg@mendix.com>
>> To: "Nikolay Borisov" <nborisov@suse.com>, "Su Yue" <suy.fnst@cn.fujitsu.com>, linux-btrfs@vger.kernel.org
>> Subject: Re: [PATCH] btrfs: Add more details while checking tree block
>>
>> On 06/22/2018 01:48 PM, Nikolay Borisov wrote:
>>>
>>>
>>> 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)
>>
>> From a user support point of view, this text should really be improved.
>> There are a few places where 'want' and 'have' are reported in error
>> strings, and it's totally unclear what they mean.
>>
> Yes. The strings are too concise for users to understand errors.
> Developers always prefer to avoid "unnecessary" words in logs.
> 
>> Intuitively I'd say when checking a csum, the "want" would be what's on
>> disk now, since you want that to be correct, and the "have" would be
>> what you have calculated, but it's actually the other way round, or
>> wasn't it? Or was it?
> For csum, you are right at all.
> 
> In this situation, IIRC bytenr of "have" is read from disk.
> Bytenr of "want" is assigned while constructing eb, from parent ptr
> , root item and other things which are also read from disk.
>>
>> Every time someone pastes such a message when we help on IRC for
>> example, there's confusion, and I have to look up the source again,
>> because I always forget.
> 
> Me too.
>>
>> What about (%llu stored on disk, %llu calculated now) or something similar?

Wha tabout expected got

>>
> "(%llu stored on disk " part sounds good to me. But I don't know how to 
> describe the second part. May the good sleep help me.
> 
> Thanks,
> Su
>>>
>>>> +			     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;
>>>>  	}
>>>>
>>
>> -- 
>> Hans van Kranenburg
>> --
>> 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
>>
> 

  reply	other threads:[~2018-06-22 16:25 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
     [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 [this message]
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=1d838113-c2be-c80a-4238-8d2c52b3663c@suse.com \
    --to=nborisov@suse.com \
    --cc=Damenly_Su@gmx.com \
    --cc=hans.van.kranenburg@mendix.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