# It seems that the new feature “save-state-resume GC filewalker” isn’t functioning as expected

**URL:** <https://forum.storj.io/t/it-seems-that-the-new-feature-save-state-resume-gc-filewalker-isn-t-functioning-as-expected/25874>\
**Category:** troubleshooting\
**Tags:** filewalker\
**Created:** [April 16, 2024, 5:47pm UTC](https://forum.storj.io/t/it-seems-that-the-new-feature-save-state-resume-gc-filewalker-isn-t-functioning-as-expected/25874 "2024-04-16T17:47:00Z")\
**Posts on this page:** 1\
**Showing post:** 19

<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 26, 2024, 7:39am UTC](https://forum.storj.io/t/it-seems-that-the-new-feature-save-state-resume-gc-filewalker-isn-t-functioning-as-expected/25874/19 "2024-04-26T07:39:52Z")

</div>

I thought It’s resolved?

> [@Turning off used space filewalker](https://forum.storj.io/t/turning-off-used-space-filewalker/25954/2):
>
> Try to use a different notation: --storage2.piece-scan-on-startup=false \ --pieces.enable-lazy-filewalker=false \ Make sure that they are provided after the image name.

---

_[View the full topic](https://forum.storj.io/t/it-seems-that-the-new-feature-save-state-resume-gc-filewalker-isn-t-functioning-as-expected/25874)._