When will "Uncollected Garbage" be deleted?

[Alexey]

@AussieNick

WARN collector unable to delete piece

This is only mean that the Garbage Collector has moved them to the trash already. This may happen, if the client deleted the TTL data before it expired, and there is an easy check:

V58 db migrate fail - piece_expiration.db - 1.108.3

If the garbage collector has been moved the piece to the trash, it will not be found by the collector. It’s pretty easy to check, search for the piece ID in the trash (remove 2 first characters): find /mnt/storj/storagenode/storage/trash -type f -iname JZRTIJAPEHJ67GI6RFHTWJTRT5FWTC7NTVDZGJXANP7ZN542AA.sj1 You may also limit to the subfolder of each satellite (there you can see the names of the folders: Satellite info (Address, ID, Blobs folder, Hex)). But likely @nerdatwork is correct and t…

@AussieNick

For some reason the trash size on the dashboard didn’t update, and it still shows 0.

this is a bug in the current version. You may restart the node to allow the used-space-filewalker update the trash usage.

@AussieNick

using du -sh.

You need to use du -s --si instead, because the dashboard showing numbers in SI (base 10).

@AussieNick

So your saying that we simply need a larger bloom filter from the satellite? Is that in the works? will that happen?

It’s happening already. Search for retain and Prep|Move.