Problem/Justification
Currently the WebGUI does not provide info on how much space is left on Optional VDEVs (i.e. metadata)
Impact
Running out of space on optional VDEVs is….. ‘not good’, so knowing how much space is left to act before this turns into an issue is helpful.
Should also trigger alerts (if that isnt already the case)
User Story
Especially with 26.04 allowing larger files to get placed on the metadata special vDEV, the risk of running out of space on it increases.
It would be beneficial to see the usage in the Storage Dashboard.
Got any mockups or ideas of how you might envision it looking?
Side note: Running out of space on the special vdev class is “less not good” than normal circumstances, because allocation will spill over onto primary vdevs. This does come with a performance penalty, but your pool won’t commit sudokuSubaru stop working because of it.
There’s also a default parameter that stops alloc of non-metadata when the pool hits (default) 25% of space free, so your allocations may stop sooner than you think, especially (heh) in pools where you’re also depending on special to be your SLOG device.
Oh that is great!
All info I found so far suggested that you can run out of space on the optional vdevs and then you cannot write anymore to your pool.