# 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:** 59

<div class="post-metadata">

**Author:** ![jammerdan](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/jammerdan/32/1121_2.png) [@jammerdan](https://forum.storj.io/u/jammerdan)\
**Post date:** [June 13, 2024, 12:02pm UTC](https://forum.storj.io/t/it-seems-that-the-new-feature-save-state-resume-gc-filewalker-isn-t-functioning-as-expected/25874/59 "2024-06-13T12:02:09Z")

</div>

> [@elek](#):
>
> but won’t solve fully the problem

Here is one problem I have now as I had to turn off the regular filewalker:

> [@Overriding available space?](https://forum.storj.io/t/overriding-available-space/26621):
>
> I had to disable the filewalker on this node as it would not finish. Now of course the used space is not correct and I cannot let it correct it. The node believes it is full, however according to df there it 1.4 TB free. It does not accept any more uploads. But I cannot raise the available space due to this change I guess: as it is already at max space. So no matter what I enter in the docker run command, it remains at the max disk size. So what can I do, is there a way to override this?

I should be gone with the save-state-resume feature working.

---

_[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)._