Why such low ingress

[Alexey]

@YuriyGavrilov

satPiecesContentSize < 0

This is only mean that the used-space-filewalker didn’t finish its job for this particular satellite. Please enable the scan on startup if you disabled it and restart the node, then wait until it will be finished for all trusted satellites:

Filewalker status

Logs should be at least info level Used space filewalker Task: Calculates disk usage by scanning all pieces and updates the local node databases afterwards with these values docker logs storagenode -f 2>&1 | grep "used-space-filewalker" | grep -E "started|finished" GC filewalker Task: Based on a Bloom filter it marks pieces as expired for removal by the retain process docker logs storagenode -f 2>&1 | grep "gc-filewalker" | grep -E "started|finished" Trash-cleanup filewalker docker logs sto…

If it would fail with a “context canceled” error, then try to disable the lazy mode, save the config and restart the node. The used-space-filewalker should finish its job for all trusted satellites successfully to update databases. And as a result the dashboard.

Please do not forget to remove the untrusted satellites’ data:

How To Forget Untrusted Satellites

Following the announcement to decommission Europe-north-1 and US2 satellites, manually deleting the remaining data of these satellites from the node can be a tedious task as it requires finding the blobs folder name for each satellite, so we wanted to improve the storagenode CLI to semi-automate cleaning up a satellite data after it is marked as untrusted. The storagenode CLI (versions from 1.88.0) provides a forget-satellite subcommand to remove satellites from the trust cache and clean up the…