Of 1,451 TiB of raw flash, 47 TiB holds data. Hosts have been given 1,703 TiB of thin volumes.
A quarter of raw capacity goes to RAID parity before a pool exists, and 950 TiB (65%) sits free in the pools. Data reduction turns the 179 TiB that hosts wrote into 34 TiB stored. On the virtual side, the arrays have provisioned 2,918 TiB of thin volumes, 2.9 times their pool capacity: 1,703 TiB presented to hosts and 1,145 TiB mapped to no host. Snapshot and clone volumes are left out, because the space they use is already in pool usage.
1,450.6TiB
Raw flash
Seven parity groups, before RAID
47.2TiB
Physically used
3.3% of raw, 4.7% of pool capacity
145.1TiB
Saved by data reduction
179 TiB written, 33.8 TiB stored: 5.3 : 1
1,703TiB
Presented to hosts
1.7× the 997 TiB of pool capacity; snapshots and clones excluded
RAID parity takes 363 TiB, exactly 25% of raw, on every array. All seven parity groups are RAID6 6D+2P or RAID5 3D+1P, and both lose one drive in four.
Array C's Pool 0 has provisioned 1,412 TiB on 164 TiB of pool capacity, 8.6 times over, while storing 26 TiB. 1,022 TiB of it is presented to ESX-08. No other pool exceeds 3.3 times.
Zero-page reclaim, not compression, accounts for most of the saving: 95.5 of 145 TiB, and 83.2 TiB of that on Array B Pool B0 alone.
Each pool on Arrays A and B holds back 22 to 23 TiB of its parity group (91 TiB in all). Array C pools take their parity groups whole. The API does not report what the Array A/B reserve is for.
Figure 1 · Physical flow
Capacity narrows from 1,451 TiB raw to 47 TiB used, then data reduction widens it back to 179 TiB written
Where each array's raw capacity goes, left to right
Band height is capacity, on one scale shared by all three arrays. Branches that drop below the band leave it; branches that join from above are data hosts wrote that the array did not need to store. Percentages are of each array's raw capacity.
Figure 2 · Virtual flow
Of 2,918 TiB provisioned, 58% is presented to hosts, nearly all of it VMware, and 39% is mapped to no host
Primary thin volume capacity from array to pool to who it is presented to (TiB)
Width is provisioned capacity of primary volumes, on a scale several times smaller than Figure 1. Against each pool, "written" is what hosts have written and "stored" is what that occupies after data reduction. Host groups smaller than the top seven are combined into Other hosts.
Detail
Per pool, Array C Pool C0 is the most over-provisioned, at 8.6 times its capacity
TiB unless shown. Reduction is written ÷ stored. Provisioned is primary thin volumes only; Snapshots & clones is the nominal size of the Thin Image secondaries left out of it. Provisioned ÷ pool compares provisioned capacity with the pool's own capacity. C-Pool 2 has no thin volumes.