Striping
Split data into chunks and distribute them across drives. Multiple members can work in parallel. Striping alone provides no extra copy.
IDLE
Space start / pause
| File | Allocated | Blocks | Fragments | Largest extent | In place | Extent writes | Bytes written |
|---|
RAID means Redundant Array of Independent Disks. It combines drives into a logical array. The level determines how data is spread, how much capacity remains usable, and which drive failures the array can tolerate.
Split data into chunks and distribute them across drives. Multiple members can work in parallel. Striping alone provides no extra copy.
Keep identical data on separate drives. A surviving mirror member can supply the copy when its partner fails.
Store calculated recovery information alongside data. Missing data can be reconstructed from surviving members, within the level’s failure tolerance.
Click a drive to fail it; click again to restore it.
Failure tolerance:
This small example illustrates failure patterns. It is separate from your defrag run; restoring a button does not model rebuilding a real drive.
| Level | Usable capacity | Drive losses tolerated |
|---|
N = member drives; D = capacity of the smallest member; G = RAID 6 groups; M = drives per group. Formulas assume equal drives, two-way mirrors, and equal group sizes. Filesystem overhead and hot spares are excluded.
RAID 10 survives one failed drive in each mirror pair, but losing both members of one pair makes the array unavailable. RAID 60 survives two failures in each RAID 6 group, but three failures in the same group exceed its redundancy. Try both patterns above.
Defragmentation rearranges fragmented file extents into more contiguous positions. RAID distributes those logical positions across its members. Rebuilding reconstructs data onto a replacement drive after a failure; it is a different operation. HDD defragmentation can reduce scattered access. SSD optimization commonly uses TRIM instead of the same HDD routine. The game models logical relocation; its random stalls and displayed rates are not hardware benchmarks.
Redundancy helps keep data available through certain drive failures. It does not provide an independent history of files: deletion, unwanted changes, or corruption can affect the array’s copies too. A separate backup provides a recovery path for those events.