Re: Errors found in extent allocation tree (single bit flipped)

[Qu Wenruo <quwenruo.btrfs@gmx.com>]

在 2024/8/20 23:31, Pieter P 写道:
> On 12/08/2024 16:57, Pieter P wrote:
>> Can this problem be fixed by running btrfs check --repair from a live
>> USB? (I'm using Ubuntu 22.04 with btrfs-progs v5.16.2).
>
> Turns out, the answer is no :(
> I tried this on (a copy of) a backup image of the corrupt file system,
> and btrfs check --repair simply failed in step [2/7].

The corruption is not in extent tree, but seemingly inside the subvolume
tree.

And in that case, "btrfs check --mode=lowmem" output may help a little
more, and the same for "btrfs check --repair --mode=lowmem".

>
> 1. What should my next move be? How can I fix my file system?

If above lowmem mode still doesn't work, I can craft a tool for your
specific corruption if really needed.

But that will need the dump of your subvolume 257 inode 50058751.


> 2. Or if that's not possible, how to figure out which files may be
> lost/corrupt when copying everything to a fresh btrfs partition?

Subvolume 257, inode 50058751.


> 3. When creating a new file system, can I somehow "clone" the subvolumes
> on my current file system (e.g. @ and @home, and the dozens of
> subvolumes created by Docker)?

Btrfs send should still be fine, except subvolume 257.

Thanks,
Qu

>
> Thanks,
> Pieter
>
>