But look, there are several different manifestations of the issue.
You know when @thepaul wasn’t even aware of additional ones:
I don’t know if this is onlyl one issue with the same cause as I see several different manifestations where each might require a different approach to get rid of it. So one thing is to make devs aware of the wide range of weird outcomes in the trash.
That’s one thing. The other thing is that I would like to know if Storj is going to offer an automatic solution to fix this. I mean they would have to deal with all those variations that I am not sure if there is an easy fix (Well, there is).
All we have seen so far is the suggestion from @clement to manually sort it out:
It might be possible that the node downgraded at some point. I would suggest you move the trash for the satellite to a new folder with the current date: rename the satellite trash folder to a temp name mv /storage/trash/ukfu6bhbboxilvt7jrwlqk7y2tapb5d2r2tsmj2sjxvw5qaaaaaa /storage/trash/ukfu6bhbboxilvt7jrwlqk7y2tapb5d2r2tsmj2sjxvw5qaaaaaa-2024-05-17 create a new folder for the satellite in the trash: mkdir -p /storage/trash/ukfu6bhbboxilvt7jrwlqk7y2tapb5d2r2tsmj2sjxvw5qaaaaaa move the…
to which even @BrightSilence had objected.
But what we don’t have is a word from Storj that this is going to be fixed, so don’t touch it, there is no issue on Github that somebody is working on it or when to follow progress.
And again the worst thing is happening: Trash does not get deleted, blocking new ingress on full nodes. And the case that garbage accumulates without getting deleted is the one big issue from recent problems and we hoped we don’t see something like this again soon.