bit error = lost file, reduce BER how?

[m^2]

I'll try:

RAID 5, you have to tell it which bit to favor, parity or original data. This means no real protection other than preventing corrupt volumes.

RAID 6, there are 3 bits and the odds of 2 bits being bad are small, therefore when the bad data is fixed, odds are good it really was the bad data and you are doing the equivalent of a coin toss.

RAID 6 of 3 drives doesn't make sense. You have most likely 6-24 drives. And have to choose 1. Assumption that there's only 1 error is reasonable. With it the second parity lets you halve (?) number of drives that are suspected. So you have 8-33% of guessing correctly.

As far as RAM bit errors, the original Corsair rule I recall is: 1 bit error occurs in 256MB of ram every month.
4GB = 15 bit errors/month
8GB = 31 bit errors/month
16GB = 62 bit errors/month
32GB = 125 bit errors/month

However, other more recent sources maintain 1 bit error per gigabyte per month, so that cuts those numbers by a factor of 4, i.e.:
4GB = 4 bit errors/month
8GB = 8 bit errors/month
16GB = 15 bit errors/month
32GB = 31 bit errors/month

Which is more correct? My guess is that it's somewhere in between, governed by the quality of the RAM, amount of overclock beyond stated specs, the luck of the draw, and a host of other issues.


Anyone with more up to date or correct info please feel free to correct me.

Thanks, I knew the Corsair data, but not the other one. But this applies to non-ECC memory. ECC has some error rate too - a double error in not correctable. Taking the data above and calculating chance if double error is wrong as ECC memory has more modules - how many? Depends on implementation.

Anyway that's not what I was looking for - I'm curious how is it if you take computer as a whole, add standard protection (RAID+ECC mem+ECC controller cache), pump data constantly for a year or 2 and then verify the output. I didn't expect that you'll know of such data, but it doesn't hurt to ask.