RAID capacity·JBOD · 22disks
JBOD · 22disks
22disks
Capacity efficiency 100%

JBOD with 22 disks — 22 usable

22 disks in JBOD give you 22 disks’ worth, with 0 spent on parity or mirroring. That is 100% efficiency, and it always survives 0 failures.

Disks
22
Usable disks
22
Spent on parity or mirror
0
Capacity efficiency
100%
Failures always survived
0
Best case
0
Groups
1
Disks per group
22

JBOD

The disks are simply concatenated into one volume. No parity, so no failure is survived — but a dead disk takes only its own data with it.

TB on the label, TiB on the screen

  • 1 TB × 2222 TB · 20.01 TiB
  • 2 TB × 2244 TB · 40.02 TiB
  • 4 TB × 2288 TB · 80.04 TiB
  • 6 TB × 22132 TB · 120.05 TiB
  • 8 TB × 22176 TB · 160.07 TiB
  • 10 TB × 22220 TB · 200.09 TiB
  • 12 TB × 22264 TB · 240.11 TiB
  • 14 TB × 22308 TB · 280.12 TiB
  • 16 TB × 22352 TB · 320.14 TiB
  • 18 TB × 22396 TB · 360.16 TiB
  • 20 TB × 22440 TB · 400.18 TiB
  • 22 TB × 22484 TB · 440.2 TiB
  • 24 TB × 22528 TB · 480.21 TiB

One TB on the box is 10¹² bytes, while the operating system counts in units of 2⁴⁰ bytes. The names look alike but the units differ, so the same disk reads about 9% smaller. Nothing went missing — the ruler changed.

Same disk count, other levels

Same level, other disk counts

The rebuild is the dangerous part

When a single-parity array loses a disk, you put a new one in and every remaining disk is read end to end to rebuild it. That is precisely when the survivors work hardest and longest. The bigger and more numerous the disks, the longer the rebuild — days, sometimes — and a second failure during it ends the array. This is why RAID 6 or 10 is preferred over RAID 5 on large arrays.

How to read it

  • Usable = total − parity × groups. Every level is that one line.
  • RAID 5 spends one parity disk in a single group, so n−1; RAID 6 spends two, so n−2.
  • RAID 50 and 60 run several such groups striped together, so the parity is multiplied by the group count.
  • RAID 1 holds one copy on every disk, so one disk’s worth; RAID 10 mirrors in pairs, so half.
  • Groups must be equal in size, so the group count can only be a divisor of the disk count.
  • TB on the box and TiB on the screen are different units — about 9% apart.

RAID is not a backup

RAID protects against exactly one thing: a disk dying. A file deleted by mistake, a file overwritten, ransomware, a failed controller, fire or theft all propagate to every disk at once — a mirror deletes just as faithfully as it writes. A backup is a separate copy on separate hardware, and RAID is not doing that job.

Common questions

Q. How much do 22 disks give in JBOD?

22 disks’ worth. 0 go to parity or mirroring, for 100% efficiency.

Q. How many failures does it survive?

0 always, and up to 0 if they land in the right places.

Q. How many TB with 4 TB disks?

88 TB, which the operating system shows as 80.04 TiB — different units, same bytes.

Q. What is this level?

The disks are simply concatenated into one volume. No parity, so no failure is survived — but a dead disk takes only its own data with it.