# Two weeks working for free in the waste storage business :-(

**URL:** <https://forum.storj.io/t/two-weeks-working-for-free-in-the-waste-storage-business/26854>\
**Category:** troubleshooting\
**Tags:** garbage-collector\
**Created:** [June 28, 2024, 4:22pm UTC](https://forum.storj.io/t/two-weeks-working-for-free-in-the-waste-storage-business/26854 "2024-06-28T16:22:36Z")\
**Posts on this page:** 1\
**Showing post:** 143

<div class="post-metadata">

**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\
**Post date:** [July 11, 2024, 4:04am UTC](https://forum.storj.io/t/two-weeks-working-for-free-in-the-waste-storage-business/26854/143 "2024-07-11T04:04:01Z")

</div>

My nodes received the BF for SLC too, but the date is more recent

```auto
2024-07-09T19:15:29Z INFO retain Prepared to run a Retain request. {"Process": "storagenode", "cachePath": "config/retain", "Created Before": "2024-06-30T14:28:54Z", "Filter Size": 6496965, "Satellite ID": "1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE"}

```

> [@Mad\_Max](#):
>
> So GC couldn’t remove anything before the TTL collector for SL.

Likely a vice versa, you likely have had WARNs from the `collector` (it’s a TTL collector), the GC one is called `gc-filewalker` and `retain`.

However, since you received a BF for the older date, then perhaps you are correct and TTL collector could be faster.  
My nodes have had dozens WARNs related only to the `collector`, not `gc-filewalker` or `retain`. Well, they actually have had a one WARN though too, but not dozens as for `collector`.

> [@Mad\_Max](#):
>
> So I think my first guess that the reason (or one of the reasons) is that the records of deleted TTL pieces are not being deleted properly from the database is correct.

Yes, it’s a known bug and should be fixed in 1.108.x as far as I know,

> [@Updates on Test Data](https://forum.storj.io/t/updates-on-test-data/26034/1679):
>
> Not on the nodes… It seems deleting expired TTL pieces does not update the used space stats.

And I added your comment about `piece_expiration.db` to the issue

> <https://github.com/storj/storj/issues/7025>
>
> Source: https://storj.slack.com/archives/C071RHTMU75/p1719831267969909 
> 
> Per Kal…yon: We have an issue with how we delete TTL pieces from the storage nodes. All my storage nodes are full since Friday and stopped receiving new uploads. Over they weekend they deleted a few hundred GB of TTL pieces, but the reclaimed space is not reported as free to the satellites, so still no new uploads. It seems deleting expired TTL pieces does not update the used space stats.
> 
> 
> \`\`\`\[tasklist\]
> \### Tasks
> \- \[x\] Understand what's occurring and why
> \- \[\] cherry-pick this fix and restart the rollout with a new version
> \`\`\`

---

_[View the full topic](https://forum.storj.io/t/two-weeks-working-for-free-in-the-waste-storage-business/26854)._