linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/3] btrfs-progs: check: enhance the csum mismatch error message
Date: Thu, 26 Aug 2021 14:28:15 +0200	[thread overview]
Message-ID: <20210826122815.GL3379@twin.jikos.cz> (raw)
In-Reply-To: <20210826064036.21660-1-wqu@suse.com>

On Thu, Aug 26, 2021 at 02:40:33PM +0800, Qu Wenruo wrote:
> This patchset will change the csum mismatch error message for data csum
> mismatch, from the old almost meaningless output:
> 
>   [5/7] checking csums against data
>   mirror 1 bytenr 13631488 csum 19 expected csum 152 <<<
>   ERROR: errors found in csum tree
> 
> To a more human readable output:
> 
>   [5/7] checking csums against data
>   mirror 1 bytenr 13631488 csum 0x13fec125 expected csum 0x98757625
>   ERROR: errors found in csum tree
> 
> Qu Wenruo (3):
>   btrfs-progs: move btrfs_format_csum() to common/utils.[ch]
>   btrfs-progs: slightly enhance btrfs_format_csum()
>   btrfs-progs: check: output proper csum values for --check-data-csum

Nice, added to devel, thanks.

  parent reply	other threads:[~2021-08-26 12:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-26  6:40 [PATCH 0/3] btrfs-progs: check: enhance the csum mismatch error message Qu Wenruo
2021-08-26  6:40 ` [PATCH 1/3] btrfs-progs: move btrfs_format_csum() to common/utils.[ch] Qu Wenruo
2021-08-26  6:40 ` [PATCH 2/3] btrfs-progs: slightly enhance btrfs_format_csum() Qu Wenruo
2021-08-26  6:40 ` [PATCH 3/3] btrfs-progs: check: output proper csum values for --check-data-csum Qu Wenruo
2021-08-26 12:28 ` David Sterba [this message]
2021-08-26 12:50   ` [PATCH 0/3] btrfs-progs: check: enhance the csum mismatch error message 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=20210826122815.GL3379@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=wqu@suse.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).