Re: BTRFS errors following bad SATA connection

[Roman Mamedov <rm@romanrm.net>]

On Thu, 2 Jan 2025 10:32:43 +0100
Victor Banon <banon.victor@gmail.com> wrote:

> So I understand I possibly have 1000 corrupted files somewhere with no way
> of identifying which without using a backup for comparison.

Btrfs stores checksums for data, so unless you turned that off, reading
corrupted files will return an I/O error, not bad content. So you can just
reread all files into /dev/null, and the corrupted ones will be unreadable.

Overall for your FS it's not looking good, there is no proper fix for "parent
transid verify failed" and this may require a reformat.

I remember reading something about the mdadm RAID5 making this issue of Btrfs
worse, due to mdraid "write hole", which its PPL feature is supposed to fix.

Basically, while with one disk it's either "written" or "not", with mdraid it
could be written on some disk but not on others, and it may present older
portion of the ondisk state to the FS, where all breaks loose.

-- 
With respect,
Roman