From: Martin Steigerwald <martin@lichtvoll.de>
To: linux-btrfs@vger.kernel.org
Subject: parent transid verify failed + level verify failed
Date: Sun, 19 Nov 2023 12:34:44 +0100 [thread overview]
Message-ID: <9221302.CDJkKcVGEf@lichtvoll.de> (raw)
Hi!
Have a great Sunday and absolutely feel free to reply at a later time :)
After having used linux-6.7-rc1 almost rc2, git commit
791c8ab095f71327899023223940dd52257a4173 in order to test out BCacheFS,
back on 6.6.1 after two attempts of non working hibernation and a strange
experience with GRUB presenting its command prompt instead of a boot menu¹,
I now got this funny stuff:
[ 1849.408572] BTRFS error (device dm-1: state EA): parent transid verify failed on logical 1178386432 mirror 1 wanted 538478 found 538901
[ 1849.408943] BTRFS error (device dm-1: state EA): level verify failed on logical 1132724224 mirror 1 wanted 0 found 1
[ 1849.414073] BTRFS error (device dm-1: state EA): parent transid verify failed on logical 1178386432 mirror 1 wanted 538478 found 538901
[ 1849.446144] BTRFS error (device dm-1: state EA): parent transid verify failed on logical 1204469760 mirror 1 wanted 538478 found 538904
[ 1849.448792] BTRFS error (device dm-1: state EA): parent transid verify failed on logical 1204469760 mirror 1 wanted 538478 found 538904
[ 1849.449515] BTRFS error (device dm-1: state EA): parent transid verify failed on logical 1204469760 mirror 1 wanted 538478 found 538904
[ 1849.451647] BTRFS error (device dm-1: state EA): parent transid verify failed on logical 1204469760 mirror 1 wanted 538478 found 538904
[ 1849.454860] BTRFS error (device dm-1: state EA): parent transid verify failed on logical 1204469760 mirror 1 wanted 538478 found 538904
[ 1849.455527] BTRFS error (device dm-1: state EA): parent transid verify failed on 2a006853-bec0-4026-94aa-8ade2e0c3674logical 1204469760 mirror 1 wanted 538478 found 538904
[ 1849.456286] BTRFS error (device dm-1: state EA): parent transid verify failed on logical 1204469760 mirror 1 wanted 538478 found 538904
Noticed as BTRFS for / went read only.
Kernel 6.6.1 on Devuan Ceres on ThinkPad T14 AMD Gen 1 32 GiB RAM with
2 TB Samsung 980 Pro NVME SSD.
I cannot do a scrub cause despite
WARNING: failed to write the progress status file: Read-only file system. Status recording disabled
scrub started on /, fsid […] (pid=31693)
scrub does not seem to do anything.
Will now boot into GRML and recover from backup, also checking the other
BTRFS filesystems.
While focus will be to get to a full working state as quickly as possible,
I intend to do a full dd copy for forensic analysis.
[1] Described in more detail at the end of:
Re: Questions related to BCacheFS
https://lore.kernel.org/linux-bcachefs/2273246.iZASKD2KPV@lichtvoll.de/T/#m3fc22fb92f1f2d160f2b3a2387dc1f10d067fb97
Best,
--
Martin
next reply other threads:[~2023-11-19 11:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-19 11:34 Martin Steigerwald [this message]
2023-11-19 16:41 ` parent transid verify failed + level verify failed Martin Steigerwald
2023-11-19 18:41 ` Martin Steigerwald
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=9221302.CDJkKcVGEf@lichtvoll.de \
--to=martin@lichtvoll.de \
--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