No important fix in 1.144.4.
You don’t need multinode, all information is already available via localhost:debugport/metrics or SNO rest API.
Some important metrics (from /metrics):
used_space: the used space calculated by the actual space reporter (either dedicated or shared)satellite_usage: this is the useful bytes according to the satellite (doesn’t include trash, overhead). This is calculated on satellite side (but shared with storagenode)hashstore{field="LenLogs")cumulative size of log fileshashstore{field="LenSet"}The useful data in the DB of the hashstore. Lenlogs can be bigger, as it can also contains dead data (until following compactions)
it not update new income data.
it only updates it after restart.
So it write disk full till the end.
This is not what we experience with our nodes, and recent change should have affect only on the UI.
Wondering if you run active migration, it is possible that that’s the one which is filling the disk?