2.87 TB in trash

Node Operators
1

Hello friends,

I do have a question - just checked my node (don’t look too often) and have seen that the Trash is HUGE. I didn’t do any further checks if this is just a visualization bug?
Also the node is on v1.82.1 so updating works, also has been restarted for this update some days ago.

I’m not so active any more so don’t know how I could / should check myself or maybe trigger garbage collection (not even sure this is still the case, I do remember that there was a change on this recently?)

I searched a bit but all big t rash discussion where from 2020 so pretty old.

Thanks for your help!

Look here:

image
image1732×946 66.8 KB

2
3 Likes
3

We see the same thing.
There was a bug where bloom filter was not marking all the removed files for deletion, which was recently fixed.
And then this: Announcement: Storj to shut down europe-north-1 and us2 - Announcements - Storj Community Forum (official).

4 Likes
4

Thanks you two.
So that means - just leave it / let it do the job and it should go down over time again right?
Nothing more to be done.

3 Likes
5

Correct.
20 characters.

1 Like
6

I believe the pieces are kept in trash for a week and than they are permanentely deleted.

4 Likes
7

Does the solution have to do something with the node version? Is it in 1.81.3 or 1.82.1 solved?

8

No, it was a change on the Satellites but I believe it was rolled out around the same time 1.82.1 was moved to recomennded.
The change that was in Storagenode 1.82.1 software was the fix for the ingress graph, but it isn’t related to GC or trash.

1 Like
9

My 1.08TB has just moved from Trash to Free :slight_smile:

2 Likes
10

Yeah same here.

image
image1728×948 56.1 KB

And took quite some CPU on my Synology :slight_smile:

image
image1114×520 22.1 KB

Obviously:

image
image1088×988 64.3 KB

But glad it worked out and ran through nicely.