@iska@mk.starnix.network I've migrated from #btrfs to ext4 on my laptop today. Yeah, I know, but I've never used any of the advanced features and ext4 is a tiny bit more performant. I've seen read errors very similar to the ones you've had. I did some reading and looks like it's the way btrfs works: when there is a checksum mismatch, the filesystem just marks the file unreadable forever instead of returning the corrupt data. There is no way to fix it the ext4-way, you can only overwrite the file