Hello @edortaprz,
Welcome to the forum!
@edortaprz @xgDkAbzkp9yi
It can be, but when the used-space filewalker would finish the scan it should update databases. Check that there is no errors related to neither of them in your logs and that’s all used-space-filewalkers are finished their scan for each trusted satellite. The databases have a flush interval of 1h by default, so do not restart the node earlier, than after the hour is passed since finished filewalkers.
In addition, you need to use SI measure units (base 10) to check the usage by the OS:
df --si -T
This is valid only for the case, if you provided the whole disk, not a part of it. Otherwise you need to use du --si instead.
@xgDkAbzkp9yi the Avg used space is unrelated to a local usage, it’s reported from the satellites. Accordingly your graph, some satellites didn’t send reports about their usage.
It’s also the expected behavior in the beginning of each month. This information is updated once per 12h by default on the nodes and once per 24h on the satellites (if their chore can keep up and would finish before the next day, otherwise you could see gaps, see Avg disk space used dropped with 60-70%). This is not a bug on the satellite, but inconvenient UI issue on the node. The feature to ignore gaps: