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

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

在 2024/8/27 16:21, Qu Wenruo 写道:
>
>
> 在 2024/8/27 14:49, Qu Wenruo 写道:
>>
>>
>> 在 2024/8/27 10:17, Pieter P 写道:
>>> On 27/08/2024 01:18, Qu Wenruo wrote:
>>>> After your latest --repair try, the fs should be more or less fine, you
>>>> can try remove the offending file.
>>>>
>>>> Just a minor problem left with the superblock used bytes, that can be
>>>> fixed by another "btrfs check --repair" run very safely.
>>>
>>> No luck, unfortunately. Removing the file fails (automatically gets
>>> re-mounted read-only, and the file re-appears), and btrfs check --repair
>>> fails to repair the super bytes_used error (output attached).
>>>
>>>> Another possibility is, the fs is old and you just migrated the
>>>> drive/fs
>>>> to the current platform, but I doubt about the case considering the
>>>> file
>>>> is some browser cache, which shouldn't be that old.
>>>>
>>>> Just in case, mind to try something like memtest86+ (UEFI payload) or
>>>> memtester (inside the OS) to rule out the hardware problem?
>>>
>>> The fs is only around 1.5 years old, it never left the system. The file
>>> was last modified on July 22. I'll run another memtest.
>>
>> Anyway considering it's not going to be resolved by repair, I can craft
>> a dedicated tool, if you can compile btrfs-progs.
>>
>> That should fix modify that specific file extent (root 257 ino 50058751
>> filepos 0) by changing its on-disk bytenr to the correctly.
>>
>> Will let you know when the tool is done (should be pretty soon)
>
> Here is the hand crafted fix for you:
>
> https://github.com/adam900710/btrfs-progs/tree/dirty_fixes
>
> The usage is:
>
> # ./btrfs-corrupt-block -X <device>
>
> The fs must be unmounted.

And it's better to run "btrfs check --readonly" after a successful run
(the successful should result no output), and paste the output of the
btrfs-check.

If there is something wrong, the program should output something and
please paste it here.

Thanks,
Qu

>
> Thanks,
> Qu
>
>>
>> Thanks,
>> Qu
>>>
>>> Thank you,
>>> Pieter
>>>
>>
>