# Current situation with garbage collection

**URL:** <https://forum.storj.io/t/current-situation-with-garbage-collection/25711>\
**Category:** Node Operators\
**Tags:** garbage-collector, storagenode\
**Created:** [April 2, 2024, 4:47pm UTC](https://forum.storj.io/t/current-situation-with-garbage-collection/25711 "2024-04-02T16:47:47Z")\
**Posts on this page:** 1\
**Showing post:** 186

<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:** [April 14, 2024, 12:15pm UTC](https://forum.storj.io/t/current-situation-with-garbage-collection/25711/186 "2024-04-14T12:15:04Z")

</div>

I do not think so…  
But, yes, you can run it manually (not sure could it help?):

> [@Manually start filewalker](https://forum.storj.io/t/manually-start-filewalker/25698/6):
>
> This is where the power of scripting comes in. For example (need to first uncomment the line in the config): #!/bin/bash CONTAINER\_NAME=storagenode CONFIG\_PATH=/mnt/storj/config.yaml docker container stop $CONTAINER\_NAME sed -i "s/^storage2.piece-scan-on-startup: .\*/storage2.piece-scan-on-startup: true/g" $CONFIG\_PATH docker container start $CONTAINER\_NAME sed -i "s/^storage2.piece-scan-on-startup: .\*/storage2.piece-scan-on-startup: false/g" $CONFIG\_PATH However I do agree with having more f…

However, I’m not sure that it could help with a BF, because it’s sent from the satellites… and if your node version doesn’t support to store it locally… well, it will be forced to wait for the next one.

---

_[View the full topic](https://forum.storj.io/t/current-situation-with-garbage-collection/25711)._