0 byte ingress, egress 10GB after large deletion

[baker]

Hmmm. I wonder if your issue is related to this:

API disk space used negative

With one of the latest updates it seems like the space used calc used in the storagenode API has changed. Assume the following scenario: Your node has 5TB of data stored on disk. In your config you set the storage.allocated-disk-space to 1TB. Previously it showed the used space of 5TB correctly in the API, now it shows a negative amount that im not sure how it is calculated. Anybody else seen this?

I see a bunch more trash got dumped since your last post. Are you sure you typed df -H with a capital H? Because 646 GiB = 639 GB, which is the exact amount your node is reporting as free. Which is a “symptom” of that bug. I am leaning towards this as being the problem.