linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: linux-btrfs@vger.kernel.org, dsterba@suse.cz, nborisov@suse.com
Subject: Re: [PATCH v3 0/5] Enhance tree block validation checker
Date: Fri, 6 Oct 2017 19:46:24 +0200	[thread overview]
Message-ID: <20171006174624.GA3521@twin.jikos.cz> (raw)
In-Reply-To: <20170929064849.15086-1-quwenruo.btrfs@gmx.com>

On Fri, Sep 29, 2017 at 06:48:44AM +0000, Qu Wenruo wrote:
> The patchset can be fetched from github:
> https://github.com/adam900710/linux/tree/checker_enhance
> 
> It's based on David's misc-next branch, with following commit as base:
> a5e50b4b444c ("btrfs: Add checker for EXTENT_CSUM")
> 
> According to David's suggestion, enhance the output format of tree block
> validation checker.
> 
> And move them into one separate file: tree-checker.c.
> 
> Also added a output format rule to try to make all output message
> follow the same format.
> 
> Some example output using btrfsck fsck-test images looks like:
> 
> For unagliend file extent member:
> ---
> BTRFS critical (device loop0): corrupt leaf: root=1 block=29360128 slot=7 ino=257 file_offset=0, invalid disk_bytenr for file extent, have 755944791, should be aligned to 4096
> ---
> 
> For bad leaf holes:
> ---
> BTRFS critical (device loop0): corrupt leaf: root=1 block=29360128 slot=28, discontinious item end, have 9387 expect 15018
> ---
> 
> Changelog:
> v2:
>   Unify the error string format, so it should be easier to grep them
>   from dmesg. Thanks Nikolay for pointing this out.
>   Remove unused CORRUPT() macro.
> v3:
>   Replace EIO with EUCLEAN in 2nd patch. Thanks Nikolay for pointing
>   this out.
>   Correct "btrfs-progs:" to "btrfs:" for 1st patch.
> 
> Qu Wenruo (5):
>   btrfs: Move leaf and node validation checker to tree-checker.c
>   btrfs: tree-checker: Enhance btrfs_check_node output
>   btrfs: tree-checker: Enhance output for btrfs_check_leaf
>   btrfs: tree-checker: Enhance output for check_csum_item
>   btrfs: tree-checker: Enhance output for check_extent_data_item

As the comments are mostly cosmetic, I'm going to add V3 to for-next so
we have more testing coverage and expecting v4.

      parent reply	other threads:[~2017-10-06 17:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-29  6:48 [PATCH v3 0/5] Enhance tree block validation checker Qu Wenruo
2017-09-29  6:48 ` [PATCH v3 1/5] btrfs: Move leaf and node validation checker to tree-checker.c Qu Wenruo
2017-10-06 17:34   ` David Sterba
2017-09-29  6:48 ` [PATCH v3 2/5] btrfs: tree-checker: Enhance btrfs_check_node output Qu Wenruo
2017-10-06 17:38   ` David Sterba
2017-09-29  6:48 ` [PATCH v3 3/5] btrfs: tree-checker: Enhance output for btrfs_check_leaf Qu Wenruo
2017-09-29  6:48 ` [PATCH v3 4/5] btrfs: tree-checker: Enhance output for check_csum_item Qu Wenruo
2017-09-29  6:48 ` [PATCH v3 5/5] btrfs: tree-checker: Enhance output for check_extent_data_item Qu Wenruo
2017-10-06 17:44   ` David Sterba
2017-10-06 17:46 ` David Sterba [this message]

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=20171006174624.GA3521@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=nborisov@suse.com \
    --cc=quwenruo.btrfs@gmx.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).