> Gesendet: Montag, 29. März 2021 um 13:36 Uhr
> Von: "Josef Bacik" <jo...@toxicpanda.com>
> An: "B A" <chris....@web.de>, "Chris Murphy" <li...@colorremedies.com>,
> "btrfs kernel mailing list" <linux-btrfs@vger.kernel.org>
> Cc: "Qu Wenruo" <quwenruo.bt...@gmx.com>
> Betreff: Re: Aw: Re: Re: Help needed with filesystem errors: parent transid
> verify failed
>
> I'm on PTO this week so I'll be a little less responsive, but thankfully this
> is
> just the extent tree. First thing is to make sure you've backed everything
> up,
> and then you should be able to just do btrfs check --repair and it should fix
> it
> for you.
Sadly, it does not:
# btrfs check --repair --progress
enabling repair mode
[usage warning]
Starting repair.
Opening filesystem to check...
Checking filesystem on /dev/mapper/luks-ff6e174f-4cd3-42a7-8ee5-47005dd077dc
UUID: 1a149bda-057d-4775-ba66-1bf259fce9a5
repair mode will force to clear out log tree, are you sure? [y/N]: [1/7]
checking root items (0:0parent transid verify failed on
1144783093760 wanted 2734307 found 2734305
parent transid verify failed on 1144783093760 wanted 2734307 found 2734305
parent transid verify failed on 1144783093760 wanted 2734307 found 2734305
Ignoring transid failure
ERROR: child eb corrupted: parent bytenr=1145025249280 item=14 parent level=1
child level=2
ERROR: [1/7] checking root items (0:00:00 elapsed, 2657
items checked)
failed to repair root items: Input/output error
> However I've noticed some failure cases where it won't fix transid errors
> sometimes because it errors out trying to read the things. If that happens
> just
> let me know, I have a private branch with fsck changes to address this class
> of
> problems and I can point you at that. I'd rather wait to make sure the
> normal
> fsck won't work first tho, just in case.
Since I do have plenty of backups and it seems like the filesystem is still
readable, I think I'd rather delete the filesystem and create a fresh one. I
don't want to take more of your time here, unless you do want to know more
details for testing your changes. Thanks for all the hints so far!
Many thanks altogether!
Kind regards,
Chris
