From: Martin Steigerwald <martin@lichtvoll.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: parent transid verify failed + level verify failed
Date: Sun, 19 Nov 2023 17:41:17 +0100 [thread overview]
Message-ID: <4896535.31r3eYUQgx@lichtvoll.de> (raw)
In-Reply-To: <9221302.CDJkKcVGEf@lichtvoll.de>
Martin Steigerwald - 19.11.23, 12:34:44 CET:
> 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
Finally recovered.
/ was not mountable anymore after booting into GRML. Made image with dd
and restored from backup onto a newly created BTRFS.
/home also had errors. Did not take a chance. Scrubbed it, updated a
backup with good old rsync, recreated filesystem and restored from updated
backup.
Another filesystem with larger files that only sees user space writes when I
write something to it, has been okay.
I have the following diagnostic data:
1) For /: dd image on external SSD with BTRFS, thus I can snapshot and/or
ref-link copy it around and run various diagnostic stuff on it, btrfs check
output (no repair), scrub was okay.
2) For /home: btrfs check output (no repair), scrub was okay.
3) I think I have some dmesg output from what caused the root filesystem
going read only, but I think that is the output I already posted.
SMART status of 2TB Samsung 980 Pro disk okay. I do not assume that there
is anything wrong with the device.
On what caused the corruption? No idea. Could be something wrong with that
6.7-almost-rc kernel, could be some corruption that happened on failed
hibernation attempts, could have to do something with BCacheFS albeit I
doubt it. Anyway, I am back on 6.6.1 for now and will not touch 6.7 kernel
again on this laptop before I am confident that it is is safe.
About diagnostic data: Willing to post more after the weekend. Just let me
know what you need. Of course I am not willing to upload complete dd image
somewhere, even not with just the operating system filesystem, but I can
run stuff on it and provide output. Otherwise you can have any of the btrfs
check output.
Best,
--
Martin
next prev parent reply other threads:[~2023-11-19 16:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-19 11:34 parent transid verify failed + level verify failed Martin Steigerwald
2023-11-19 16:41 ` Martin Steigerwald [this message]
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=4896535.31r3eYUQgx@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