When will trash update?

[Alexey]

To fix the current discrepancy the enabled used-space-filewalker on start is enough (you may comment out the option storage2.piece-scan-on-startup: true, because this is a default value).

But to keep the trash usage updated on your dashboard you may temporary disable the lazy mode, i.e. uncomment the option # pieces.enable-lazy-filewalker: false,
So the resulted settings change may look like:

# storage2.piece-scan-on-startup: true
pieces.enable-lazy-filewalker: false

save the config and restart the node.

When the used-space-filewalker will finish its work for all satellites, it will update databases with collected values and your dashboard should show less discrepancy. The disabled lazy mode will allow all remained filewalkers run with a normal priority and updates databases in time, so discrepancy should become negligible.
In any case you will need to wait until all of them will finish their work for all trusted satellites:

Filewalker status

Logs should be at least info level Used space filewalker docker logs storagenode -f 2>&1 | grep "used-space-filewalker" | grep -E "started|finished" GC filewalker docker logs storagenode -f 2>&1 | grep "gc-filewalker" | grep -E "started|finished" Trash-cleanup filewalker docker logs storagenode -f 2>&1 | grep "trash-cleanup-filewalker" | grep -E "started|finished" retain docker logs storagenode -f 2>&1 | grep "retain" collector docker logs storagenode -f 2>&1 | grep "collector" trash docke…