8 × 14 TB in RAID 10: the numbers
| Usable space | 56 TB (50.9 TB in Windows) |
|---|---|
| Raw space | 112 TB |
| Used for protection | 56 TB |
| Efficiency | 50% |
| Drives that can fail | 1 to 4 |
| Rebuild at 150 MB/s | 25 h |
| Rebuild at 50 MB/s (busy) | 3.2 days |
| Data read during rebuild | 14 TB |
| Read error risk, desktop drives | 67% |
| Read error risk, NAS drives | 11% |
Rebuild
Replacing a failed drive means writing a full 14 TB drive. At 150 MB/s with no other load that takes about 25 h; on a busy array running at 50 MB/s, about 3.2 days. Only the mirror partner is read, so the other drives are not stressed.
Read errors
Reading 14 TB, the chance of at least one unreadable sector is 67% with desktop drives (1 per 1014 bits) and 11% with NAS drives (1 per 1015). Nothing is left to correct it, so the affected file, or on some controllers the whole rebuild, fails. These are worst-case datasheet rates; real drives usually do better.
Our take
With 8 drives, RAID 6 gives more space (84 TB instead of 56 TB) and survives any two failures. RAID 10 is the better pick for databases and virtual machines that write many small blocks.