In all but three of the differences you posted, it is a single bit that has been flipped. There does not appear to be a pattern in which bits, or which bytes, are affected, but it is significantly more common for bits to be flipped to 1 in the corrupt file, than flipped to 0.
I cannot find a package that provides libopencv_gapi.so.4.5.5. Was this something you built yourself, or installed via pip? Do you happen to know whether the file was correct at some point in the past, and it went corrupt without being updated or intentionally written to?
ext4 does not move or rewrite files that are not modified. There is no background defragmentation or anything like that. So if the file was good and went bad it could only have happened entirely within the SD card.
If you are using the overlayfs then nothing should be writing to the filesystem at all, so the card also should not need to move or rewrite data for wear levelling. But is it possible you have other writable filesystems on the same card?
I cannot find a package that provides libopencv_gapi.so.4.5.5. Was this something you built yourself, or installed via pip? Do you happen to know whether the file was correct at some point in the past, and it went corrupt without being updated or intentionally written to?
ext4 does not move or rewrite files that are not modified. There is no background defragmentation or anything like that. So if the file was good and went bad it could only have happened entirely within the SD card.
If you are using the overlayfs then nothing should be writing to the filesystem at all, so the card also should not need to move or rewrite data for wear levelling. But is it possible you have other writable filesystems on the same card?
Statistics: Posted by jojopi — Wed Oct 09, 2024 1:22 pm