Check also my posts somewhere at the end of the thread for an easy to use command.
After that is succesful, run a startup piece scan to update the used space.
hard to accept that storj doesn’t automatically delete the leftover data.
They decided to sunset the old satellites, but did not clean up.
Only a little part of node operators are going to read this.
Just should be automatically done on storj end!!!
Then there is the technical part of it. I now know how to do it. there are a lot of people that need tutorials on how to do it. they can get a node barely to run (as i was in the past also).
Basically the running of the node is turnkey, the decommissioning on storj end … not so much.
Are you sure about this? I did not manually do anything related to satellites on any of my nodes, and each one has only four folders under blobs/. Maybe if the node was offline when the satellite was revoked the request could have been lost?
It would be an oversight, but not as dramatic as “storj did not clean up”
My nodes also cleaned up nicely, but I GE before they were decomisioned. Last month I GE again from Saltlake on some new nodes. Again the data was auto deleted.
I just ran the forget sat command to clean up databases and to have a reason to run the startup piece scan.
Your node should be online to clean-up data, when the satellites become decommissioned. After decommissioning there is no satellites remained to instruct the node, that it should clean the used space.
So, we implemented this workaround to allow to clean all remained data, when your node was not reachable during decommissioning.