From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: 4e868df3 <4e868df3@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: corrupt leaf
Date: Thu, 27 Feb 2020 16:25:56 +0800 [thread overview]
Message-ID: <587446db-5168-d91d-c1fa-c7bef48959d9@gmx.com> (raw)
In-Reply-To: <CADq=pg=g47zrfKiqGFUHOJg8=+bdSGQeawihKcVcp_BahzPT+Q@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1291 bytes --]
On 2020/2/27 下午1:59, 4e868df3 wrote:
> I updated kernels recently and now am getting a corrupt leaf error.
> The drives decrypt and mount, and I can touch a file briefly until the
> mount switches over to read-only mode. Extended SMART tests show all 6
> of my drives have a healthy status. I have a backup of the data. The
> array is configured as RAID10. As the BTRFS filesystem remains
> accessible / read-only, I am able to take an additional backup. What
> is the best way to recover from this error?
>
> [ 130.395696] BTRFS critical (device dm-0): corrupt leaf: root=7
block=2533706842112 slot=5, csum end range (68761223168) goes beyond the
start range (68761178112) of the next csum item
> [ 130.395829] BTRFS error (device dm-0): block=2533706842112 read
time tree block corruption detected
This is not something caused by a powerloss, but more likely an older
kernel, or memory corruption.
Please provide the following command dump:
# btrfs ins dump-tree -b 2533706842112 /dev/dm-0
Furthermore, btrfs check output would be appreciated to ensure that's
the only corruption.
But from the generation mismatch, it looks like there are transid
mismatch error, which could be a bigger problem than your corrupted csum
tree.
Thanks,
Qu
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-02-27 8:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 5:59 corrupt leaf 4e868df3
2020-02-27 6:30 ` Chris Murphy
2020-02-27 7:23 ` 4e868df3
2020-02-27 8:03 ` Chris Murphy
2020-02-27 8:25 ` Qu Wenruo [this message]
2020-02-28 2:28 ` 4e868df3
2020-02-28 3:01 ` Qu Wenruo
2020-02-29 15:47 ` 4e868df3
2020-03-01 0:41 ` Qu Wenruo
2020-03-01 6:11 ` 4e868df3
2020-03-01 11:40 ` Qu Wenruo
2020-03-02 6:35 ` Chris Murphy
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=587446db-5168-d91d-c1fa-c7bef48959d9@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=4e868df3@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