3 ms·
Actually it's very likely that Git is exposing a failing or unreliable underlying storage medium (or memory?). I can't find the reference for it, but b/c git i
by ramses0 5y ago
Actually it's very likely that Git is exposing a failing or unreliable underlying storage medium (or memory?). I can't find the reference for it, but b/c git is so aggressive about actually checking hashes, it sometimes exposes unreliability that gets attributed to git, but is actually the hardware.
Check for "memtester", "smartctl", and "badblocks" ... understand what they do and see if they turn up anything.
- ncmncm 5y agoPossibly, but audits have also shown Git not correctly handling file system error reports. We also have file systems not correctly handling disk error reports. Last I saw, volume managers were not passing media error reports through to file systems. And, Intel has done its part to eliminate ECC from memory and buses. I guess what I am saying is that there seems to be more than enough blame to tar everybody.