Re: BTRFS errors following bad SATA connection

[Victor Banon <banon.victor@gmail.com>]

On 03/01/2025 13:09, Roman Mamedov wrote:
> When it stops mounting :)
Ok :) So there is hope... So far the file system is usable, it just 
occasionally goes into read-only when it encounters i/o errors (like 
during a scrub for example).
> As is, surely it is easier to restore 3900 files from the backup rather than
> everything?

Absolutely! But I'm a bit worried because I've already identified and 
deleted thousands of files, and errors persisted, and new corrupted 
files kept popping up. It's possible I've been doing it wrong, so I'll 
give it a go.

How do I identify which 3900 files are mismatched so that I can delete 
them? (I'm assuming it's fine if I delete them now and restore them at a 
later date once everything is stable - some of these files are the ones 
that are not backed up anyway so I don't really have a choice)

> The problem is, it could be that the transid mismatch errors won't go away
> even if you replace all the files, or you might not be able to do so. Attempt
> to delete or otherwise manipulate some of them might fail with the same errors
> in dmesg.
So far I have had no issues deleting files, with the sole exception of 
the file in the trash bin I mentioned above. I'm not sure what to do 
about that one, apart from hoping it goes away if I fix everything else. 
Do you have any advice?
> Should not be, unless your backup system silently stores half-copied files
> into the backup until the point it got an I/O error, and does not warn you of
> the error, or you miss the warning.
>
Ok, that's good news :) Thanks a lot for all your help, I really 
appreciate it.