![]() All of these RAID levels will use a single disk to replace a failed disk and all will need to fill the one disk with data. The fundamental problem is that it takes too long to fill the large disks we are now using just to regain redundancy. ![]() ![]() A RAID6 array, thanks to its dual parity nature, can cope with two concurrent disk failures. The RAID1 or RAID5 array cannot cope with another disk failing during the rebuild. When one disk fails we use a spare disk and rebuild the redundant data, either from a mirror copy in RAID1 or from the remaining data and parity in RAID5 or RAID6. For a long time we have used RAID to protect against the failure of hard disks, storing data redundantly across a small group of disks. But, there’s another shift associated with drives of ever-increasing capacity: The move away from RAID. One part of the shift is the move to use solid state storage, which has very different characteristics to spinning disks. At the core of the shift is the fact that hard disks haven’t gotten much faster as they have gotten a lot larger. There is a fundamental shift in going on in enterprise storage. Posted on FebruKeith Ward Senior Editor & Writer Enterprise Storage Guide, Guides Why RAID Cannot Cope With Large Disks: Rebuild Times
0 Comments
Leave a Reply. |