3 ms·
I remember reading, some time ago [1] [2] about how many errors were expected without a complete failure of the HDD. I mean, the odds that you just read a rotte
by woliveirajr 10y ago
I remember reading, some time ago [1] [2] about how many errors were expected without a complete failure of the HDD. I mean, the odds that you just read a rotten byte out from your disk. And how that would be enough to cause data loss, since you don't need 3 complete failures to loose data: perhaps 1 complete failure plus 2 partial HDD failures...
And as HDD sizes grew larger, things would become complicate. To the point that the probability of loosing the second disk while still restoring the first one, since HDD sizes were so big that the time it takes to rebuild a whole 3TB disk is huge, in a environment that is in production, reading and writing things at the same time you're reconstructing the lost one.
[1] This is one of such articles: http://searchdatabackup.techtarget.com/video/Preston-As-hard-drive-capacity-grows-so-does-risk-of-data-loss http://searchdatabackup.techtarget.com/video/Preston-As-hard...
[2] this is another: http://www.zdnet.com/article/why-raid-6-stops-working-in-2019/ http://www.zdnet.com/article/why-raid-6-stops-working-in-201...
- dom0 10y agoEven with datasheet values -- rebuilding a RAID5 with 4 TB or even larger disks has a significant chance of failure (iirc about 15 % for HGST MegaScale 4 TB drives; since the BER is pretty much a constant, it will be much worse with larger drives. RAID5 probably does not make much sense with 8, 10 or 12 TB drives.).
- AstralStorm 10y agoThis is why RAID6 and similar are used. Or tree like structure of RAID10. Mostly because the probability of a HDD dying whole is lower than in part, you get much more of the extra redundancy than expected. These should be also patrolled and resilvered regularly, which should catch imminent failures too.