Re: BTRFS errors following bad SATA connection

[Roman Mamedov <rm@romanrm.net>]

On Fri, 3 Jan 2025 13:42:25 +0100
Victor Banon <banon.victor@gmail.com> wrote:

> 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?

One way that comes to mind:

find . -type f -not -exec cat "{}" > /dev/null \; -exec mv "{}" "{}.bad" \;

Then you just find or delete all files with the *.bad extension.

> > 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?

If the trash bin would be in a subvolume, you could delete the subvolume. But
then that could put the FS into read-only again, and moreover, into a state
where it goes read-only each time shortly after mounting (as the cleaner
process tries to finish the job), with no way to solve that.

-- 
With respect,
Roman