VSP 360 · Capacity runwayPool physical capacity · history 25 Aug – 16 Oct 2026 · forecast to 2031
No pool fills up before 2029. A-Pool 1 on Array A reaches its 80% depletion threshold first, around October 2028.
A-Pool 1 is 5% full but grows about 83 GiB a day, so it reaches its 70% warning threshold around July 2028, 80% around October 2028 and 100% around May 2029; depending on which part of its history the trend is drawn from, 80% falls between July 2028 and September 2030. Every other pool is more than a decade from 80% at its current rate. None of the pools can grow automatically: every parity group is already fully allocated, so more capacity means new drives.
Oct 2028
First pool at 80%
A-Pool 1; range Jul 2028 – Sep 2030
83GiB/day
Its growth rate
30-day trend; 44 over the last week
2041
Next pool at 80%
A-Pool 0, at 22 GiB a day
47.2TiB
Used of 997 TiB
All pools, after data reduction
Figure · Percent of each pool used, history and forecast
Only A-Pool 1's band reaches the threshold lines before 2031; the rest barely leave the floor
Measured, daily
Forecast range
30-day trend
70% warning · 80% depletion · 100% full
Range-frame axes: each axis line spans only the measured data, and its end ticks are the first and last measured values. The forecast is a straight line from today's usage. The dashed line uses the last 30 days' growth; the shaded band runs from the slowest to the fastest growth seen over the last 7 days, 14 days, 30 days and the full history. Thresholds are each pool's configured warning (70%) and depletion (80%) rates. A pool whose trend would cross 80% after 2031 shows the year at the right edge.
What would change the answer
The forecast assumes data reduction keeps working as well as it does today
Physical usage is measured after compression, deduplication and zero reclaim. Array B is the clearest risk: hosts have written 100 TiB to B-Pool 0, which stores 7 TiB of it, mostly because the writes were zeros. If that 100 TiB had been ordinary data, B-Pool 0 would already be about 60% full. A-Pool 1's growth also comes in steps as snapshot clones are created, so a large clone batch would pull its date forward.