From: "Raúl Sánchez Siles" <rasasi78@mailbox.org>
To: linux-btrfs@vger.kernel.org
Subject: Trying to tackle https://github.com/kdave/btrfs-progs/issues/541
Date: Fri, 10 Oct 2025 10:55:55 +0200 [thread overview]
Message-ID: <2800637.mvXUDI8C0e@prox> (raw)
[-- Attachment #1: Type: text/plain, Size: 2013 bytes --]
Hello!
After a mount error "parent transid verify failed" I went to offline check the
partition and I came accross this issue. After this, I backup all data I
could get from the partition (via btrs restore). As a sidenote I also tried
mounting with the rescue=usebackuproot with the same outcome.
Currently I have a reproducible scenario to look into the issue and provided
lack of activity in the issue I thought I may be of help to provide more
information so issue can be fixed. The btrfs consistency issue looks serious
so even in case of successful debugging I don't expect to recover access to
that partition.
OS and SW:
- Debian sid
- btrfs-progs 6.17
- linux 6.16.11
Mount error:
[ 120.652356] BTRFS: device fsid 06dc5f24-a16f-4520-993a-xxxxxxxxxxxx devid
1 transid 968758 /dev/sda3 (8:3) scanned by pool-2 (4449)
[ 120.653973] BTRFS info (device sda3): first mount of filesystem 06dc5f24-
a16f-4520-993a-xxxxxxxxxxxx
[ 120.653994] BTRFS info (device sda3): using crc32c (crc32c-x86) checksum
algorithm
[ 123.225415] BTRFS info (device sda3): start tree-log replay
[ 123.523786] BTRFS error (device sda3): parent transid verify failed on
logical 229603573760 mirror 1 wanted 968173 found 966625
[ 123.538334] BTRFS error (device sda3): parent transid verify failed on
logical 229603573760 mirror 2 wanted 968173 found 966625
[ 123.538372] BTRFS error (device sda3): failed to run delayed ref for
logical 487464960 num_bytes 4096 type 184 action 1 ref_mod 1: -5
[ 123.538383] BTRFS error (device sda3 state A): Transaction aborted (error
-5)
[ 123.538387] BTRFS: error (device sda3 state A) in
btrfs_run_delayed_refs:2159: errno=-5 IO failure
[ 123.538395] BTRFS: error (device sda3 state EA) in btrfs_replay_log:2094:
errno=-5 IO failure (Failed to recover log tree)
[ 123.544693] BTRFS error (device sda3 state EA): open_ctree failed: -5
Please CC me as I'm not subscribed to the list.
Best Regards,
--
Raúl Sánchez Siles
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2025-10-10 8:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-10 8:55 Raúl Sánchez Siles [this message]
2025-10-10 20:47 ` Trying to tackle https://github.com/kdave/btrfs-progs/issues/541 Qu Wenruo
2025-10-11 12:20 ` Raúl Sánchez Siles
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=2800637.mvXUDI8C0e@prox \
--to=rasasi78@mailbox.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.