2 ms·
eh, I bet you are wrong. I've run memtest many times, often for days, and it never detected any bitflips in RAM. And memtest is specifically designed to exerci
by theamk 4y ago
eh, I bet you are wrong.
I've run memtest many times, often for days, and it never detected any bitflips in RAM. And memtest is specifically designed to exercise every bit of memory and detect bitflips. While I've seen my share of PCs with memory errors, when you see one you replace memory / tweak settings, and then run memtest for a day or so to ensure it does not reappear.
Also, "unused memory" should not be a thing in modern PC: the read cache should expand to fill it - it's super fast to evict and provides tangible benefits in case of hit.
The errors usually occur on the boundaries - like in the network or in the SATA connection to disk or even in USB bus. For example the original "ZFS corruption" story (which seems t be gone from regular web, but I think its [0]) pretty clearly mentions damage "on the way to disk".
[0] https://web.archive.org/web/20091212132248/http://blogs.sun.com/elowe/entry/zfs_saves_the_day_ta https://web.archive.org/web/20091212132248/http://blogs.sun....
- sliken 4y agoNot sure what it is about memtest86, but in my experience it doesn't find most memory errors. I've had serious memory issues, that trigger memlogd, dmesg, or similar about EDAC/ECC errors. I try memtest86 over night, no errors. Restart the node and get more errors. This seems to happen most of the time, only in the rare case can I reproduce errors I see in a production system with memtest86 reports.