From: Sidong Yang <realwakka@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: btrfs-progs test error on fsck/012-leaf-corruption
Date: Thu, 18 Feb 2021 02:56:14 +0000 [thread overview]
Message-ID: <20210218025614.GA1755@realwakka> (raw)
Hi!
I found some error when I run unittest code in btrfs-progs.
fsck/012-leaf-corruption test corrupt leaf and check that it's recovered.
but the test was failed and demsg below
[ 47.284095] BTRFS error (device loop5): device total_bytes should be at most 27660288 but found 67108864
[ 47.284207] BTRFS error (device loop5): failed to read chunk tree: -22
[ 47.286465] BTRFS error (device loop5): open_ctree failed
I'm using kernel version 5.11 and there is no error in old version kernel.
I traced the kernel code and found the code that prints error message.
When it tried to mount btrfs, the function read_one_dev() failed.
I found that code added by the commit 3a160a9331112 cause this problem.
The unittest in btrfs-progs should be changed or kernel code should be patched?
next reply other threads:[~2021-02-18 2:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-18 2:56 Sidong Yang [this message]
2021-02-19 16:17 ` btrfs-progs test error on fsck/012-leaf-corruption David Sterba
2021-02-21 14:09 ` Sidong Yang
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=20210218025614.GA1755@realwakka \
--to=realwakka@gmail.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;
as well as URLs for NNTP newsgroup(s).