Comments on: A reason for ECC

By: Anonymous

Anonymous — Thu, 20 Aug 2015 10:48:56 +0000

Faulty memory non-ECC memory can definitely get on the disk (leading to CRC errors later on). I’ve had such a case. Same goes for non-correctable errors when using ECC memory.

By: Lazarus

Lazarus — Thu, 20 Aug 2015 07:43:46 +0000

Data corrupted in non-ECC RAM that has yet to be pushed to disk (or SSD, w/e) will still be corrupted when it does get to the filesystem.

By: Justin Sherrill

Justin Sherrill — Wed, 19 Aug 2015 17:31:54 +0000

This would be affecting RAM, not disk, so it’s not affecting the file system as much as it’s affecting memory operation. Hammer does apply checksums when moving data, so it could be noticed at that point. I’d expect it to cause errors at a level before it hits any file system, as a vague guess.

By: Anonymous

Anonymous — Wed, 19 Aug 2015 05:48:17 +0000

How does HAMMER respond to flipped bits on a system without ECC RAM? Is a flipped bit possible to detected as a change in the file system?