UPDATE Jan 1, 2020: this issue is now resolved for details see Changelog v0.28.4 https://github.com/storj/storj/releases/tag/v0.28.4 Warning: Garbage collection is interfering with free space calculation. If your storage node is full and executes garbage collection it might accept more pieces than i…

Bug is now fixed: [image] Changelog v0.28.4 (storage node only) STORJLINGS Bugfix Storage Node used space calculation The used space calculation now takes the trash folder (garbage collection) into account.

It’s data that was deleted by the uplink, but for some reason not from your node. It’s kept in trash for a week in case there is something wrong and data that shouldn’t have been deleted was removed. so it will be gone after a week.

More than 7 days have passed since the transfer to “trash” and nothing was removed … as it was 30.4GB free a week ago, so there is still 30.4 free now …

Will this trash data be deleted automatically or should I delete it myself?

do not delete any files yourself! This will lead to disqualification in short order.

Yes. Please do not delete ANY data that is related to running your storage node from ANY folder. The only exemption is when a support agent specifically tells you to remove specific files to fix an issue.

Any tdd on a fix? I am now 20% over my given allocation and growing. I can live with it for a while, but yeah…

please reduce your allocation to 500 GB asap using these instructions

I have allocation set at 500Gb already with 600+Gb reported. Not much I can do. Hence, when is there an outlook for a fix?

We have a fix that is going through dev review right now. So I would hope it will be available soon to be implemented.

Storj Community Forum (official)

UPDATE: the SNO Garbage Collection & Disqualification bug has been fixed

Announcements