Yeah the RAID1 part is weak sauce. However, my specific setup mitigates these flaws:<p>* The intention is to detect at-rest bit flips before they progressively pollute everywhere. I don&#x27;t mind if it&#x27;s not instantaneously detected on-access. I perform a nightly full scan - so there&#x27;s up to 24 hours where an at-rest bit-flip may lie undetected, but it won&#x27;t progress past that.<p>* I use ECC at all cache hierarchy levels possible, and ECC DDR, with active background scrub. So bit flips here won&#x27;t occur (with vanishingly small probability).<p>* I use software-RAID1 only. The path between DDR, thru CPU, and to storage controller is unlikely to have a bit flip. From there onwards, the data is essentially written twice, so there is vanishingly low probability of both having a bit-flip, except for systematic failure for that bit pattern in two attempts to two different disks and two different controllers.<p>So there&#x27;s still some places in the stack where errors can be introduced, but the most common areas of fault are either duplicated or covered by detection mechanisms.<p>My goal is to detect, but not correct, transport and at-rest bit flips. I&#x27;ll discard everything when an error is detected, and use backups.<p>For my next setup I&#x27;ll probably switch to a filesystem with a better end-to-end error detection story, such as ZFS, and ditch RAID altogether.