From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/3] btrfs-progs: error messages enhancement for bad tree blocks
Date: Thu, 2 Sep 2021 21:08:40 +0800 [thread overview]
Message-ID: <20210902130843.120176-1-wqu@suse.com> (raw)
When handling a corrupted btrfs image, there are tons of meaningless
error messages from btrfs-check:
incorrect offsets 8492 3707786077
Above error message is meaningless, it doesn't contain which tree block
is causing the problem, just some random expected values with corrupted
values.
On the other hand, btrfs kernel tree-checker has way better error
messages, and even more checks than the counterpart in btrfs-progs.
So let's just backport the superior tree-checker code to btrfs-progs,
with some btrfs-progs specific (but minor) modifications.
Now the error message would look more sane (although a little too long):
corrupt leaf: root=2 block=72164753408 slot=109, unexpected item end, have 3707786077 expect 8492
Qu Wenruo (3):
btrfs-progs: use btrfs_key for btrfs_check_node() and
btrfs_check_leaf()
btrfs-progs: backport btrfs_check_leaf() from kernel
btrfs-progs: backport btrfs_check_node() from kernel
check/main.c | 9 +-
check/mode-original.h | 2 +-
kernel-shared/ctree.c | 246 ++++++++++++++++++++++++++----------------
kernel-shared/ctree.h | 5 +-
4 files changed, 163 insertions(+), 99 deletions(-)
--
2.33.0
next reply other threads:[~2021-09-02 13:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-02 13:08 Qu Wenruo [this message]
2021-09-02 13:08 ` [PATCH 1/3] btrfs-progs: use btrfs_key for btrfs_check_node() and btrfs_check_leaf() Qu Wenruo
2021-09-03 14:02 ` David Sterba
2021-09-03 22:23 ` Qu Wenruo
2021-09-03 22:34 ` Qu Wenruo
2021-09-04 0:56 ` Qu Wenruo
2021-09-04 5:06 ` Qu Wenruo
2021-09-06 14:46 ` David Sterba
2021-09-02 13:08 ` [PATCH 2/3] btrfs-progs: backport btrfs_check_leaf() from kernel Qu Wenruo
2021-09-02 13:08 ` [PATCH 3/3] btrfs-progs: backport btrfs_check_node() " 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=20210902130843.120176-1-wqu@suse.com \
--to=wqu@suse.com \
--cc=linux-btrfs@vger.kernel.org \
/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