6 ms·
Note: This article is from 2007 and is quite prescient. It's completely shameful how bad the specified read error rates are now. It's to the point that if you
by ars 12y ago
Note: This article is from 2007 and is quite prescient.
It's completely shameful how bad the specified read error rates are now.
It's to the point that if you read an entire disk 4TB you have a 32% chance of one bit being wrong!
That means hard disks can no longer be considered reliable devices that return the data written to them, you now need a second layer in software checking checksums.
http://www.wolframalpha.com/input/?i=4TB+%2F+10^14+bit++in+%25 http://www.wolframalpha.com/input/?i=4TB+%2F+10^14+bit++in+%...
For extra money they sell hard disks with 10^15 reliability instead of 10^14 - this should be standard!
- logicallee 12y agolol @ "they should sell hard disks with 10^15 reliability instead of 10^14!" This is the funniest outrage I've seen in a while, just because the suggested fix is so specific and (relatively) low for the huge amount discussed. It's like saying, "It's an outrage that this drink holds only 37 ounces! For this kind of money I expect it to hold at least 38 ounces. I would pay for that." - My 4 downvoters are clearly a lot worse at math at I am. Let me spell it out for you: "Reliability of 100000000000000 is unacceptable! I need exactly 1000000000000000 of reliability (a factor 10 difference only)." If you don't see how that is funny, the problem is with you, not me. That's a hilariously specific, and small, change. "Man, having a 30% chance of a bit flipping if I read 4 TB is unacceptable. I should have to read like...40 TB for a 30% chance of a bit flip!" It's particularly funny because in the face of this being unacceptable, I would expect a solution, like error correction, that adds 5-10 orders of magnitude (many bit flips have to all happen in the same sector, by coincidence, at the already low 10^14 rate), for it to make it past the error correction layer. The other thing is that given that we're talking about ERROR RATES, I cannot possibly believe that they have it down to such a specific number as 100000000000000. It would have to be a range. You should target more than 1 order of magnitude to get something more reliable (like ECC RAM versus regular RAM). [1] Just like the error margin on 37 ounces must be like 37-40 ounces anyway. [1] first reference I found: http://lambda-diode.com/opinion/ecc-memory-2 http://lambda-diode.com/opinion/ecc-memory-2 "I computed that if you have 4 GiB of memory, you have 96% chance of getting a bit flip in three days because of cosmic rays. SECDED ECC would reduce that to a negligible one chance in six billion." That is, for example, a change of 1 per 34359738368 bits (rounding 96% to 100%) to 1 per 206158430208000000000 bits (multiplying by 6 billion). 34359738368 bits is 10^10. 206158430208000000000 is 10^20. That's the kind of change (give or take) that I was expecting parent to suggest - not one order of magnitude!
- ars 12y agoClearly math isn't your strong suit. An order of magnitude change is nothing minor. It would take the 32% chance and make it a 3.2% chance. Maybe you don't know that ^ means to the power off?
- abritishguy 12y agoAnd clearly it isn't your's either.
- judk 12y agoBut only a few years of difference with Moore's Law... Which was the point of the article.
- ars 12y agoYou probably mean: https://en.wikipedia.org/wiki/Kryder's_Law https://en.wikipedia.org/wiki/Kryder's_Law
- lindenr 12y agoDoes this mean that a 10^13 reliability has 320% chance of failure? EDIT: in any case the correct calculation should be http://www.wolframalpha.com/input/?i=%281-%2810^-14%29%29^%288*4*1024^4%29 http://www.wolframalpha.com/input/?i=%281-%2810^-14%29%29^%2... which gives a 30% chance of failure, versus http://www.wolframalpha.com/input/?i=%281-%2810^-15%29%29^%288*4*1024^4%29 http://www.wolframalpha.com/input/?i=%281-%2810^-15%29%29^%2... for a 3.5% chance.
- vacri 12y agoI think we have very different definitions of 'completely shameful'. One bit wrong in four trillion, on a device that only costs a couple of hundred dollars?
- ars 12y agoIt sounds good doesn't it? But then you compare to the size of the disk and realize that it's not actually that good. The shameful part is that they actually sell the 10^15 drives - and not for a ton more money either. They simply bin drives and the better ones are rated as 10^15. Instead of doing that they should figure out what's different in the manufacturing of those and do it across the board.
- ted_dunning 12y agoYeah... shameful. I am sure that there is something simple that all the drive manufacturers are just overlooking in their process that would take them to 10^-17 BER. When was the last time you created a physical artifact for sale? That had even just part per billion malfunction rates? It isn't as easy as these guys make it look by a long stretch.
- kelnos 12y agoEven worse/better -- one bit wrong, not byte. So one bit wrong in thirty-two trillion.
- Freaky 12y ago> It's to the point that if you read an entire disk 4TB you have a 32% chance of one bit being wrong! If this were the case, forums would be filled to the brim with ZFS users whinging about how they get CKSUM errors practically every time they scrubbed their pools. They do happen, but nothing like that frequently. > That means hard disks can no longer be considered reliable devices that return the data written to them They were never such devices in the first place if you ever valued your data enough to care. Even if your disks are perfect, your cabling, backplanes, IO controllers, drivers or memory probably aren't.
- ars 12y ago> If this were the case, forums would be filled to the brim with ZFS users whinging about how they get CKSUM errors practically every time they scrubbed their pools. They do happen, but nothing like that frequently. I'm going by what the manufacturers say - are you saying they are overestimating the error rate? Why would they do that? > They were never such devices in the first place No, I meant they would return false data instead of an error. Used to be you never got corruption, just success or fail. Now you have success, false success, or fail.
- Freaky 12y ago> I'm going by what the manufacturers say Are you really? "Non-recoverable Read Errors per Bits Read, Max", say Seagate - that just means it couldn't correct, not that it couldn't detect there was an error. > are you saying they are overestimating the error rate? Perhaps not, as a general order-of-magnitude upper-bound on a marginal drive in poor conditions, but certainly if you're interpreting it as an average. Too many people would be seeing it happen way too often to keep quiet about it otherwise. > Used to be you never got corruption, just success or fail I wish :/
- MarkSweep 12y agoI think that it's more shameful that modern operating systems are only slowly adapting file systems that can even detect that silent data corruption has occurred. EXT4, HFS+, and NTFS all make no effort to ensure the data you read back is the data you wrote. Slowly Btrfs on Linux and ReFS on Windows are becoming more prevalent. Since storage density is growing faster than most home users can use it, hopefully in the near future consumer computers will come configured to store multiple copies of their data. Instead of one day noticing that a picture is corrupted or the computer won't boot, periodicity scrubs will detect corruption before it's too late.