# Enabling the Lazyfilewalker

**URL:** <https://forum.storj.io/t/enabling-the-lazyfilewalker/22966>\
**Category:** STORJLINGS\
**Tags:** storagenode\
**Created:** [June 15, 2023, 1:37pm UTC](https://forum.storj.io/t/enabling-the-lazyfilewalker/22966 "2023-06-15T13:37:04Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![clement](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/clement/32/11821_2.png) [@clement](https://forum.storj.io/u/clement)\
**Post date:** [June 15, 2023, 1:37pm UTC](https://forum.storj.io/t/enabling-the-lazyfilewalker/22966/1 "2023-06-15T13:37:05Z")

</div>

There were several discussions and open concerns related to [filewalker](https://forum.storj.io/search?q=filewalker) processes (such as garbage collection and the used-space calculation services) competing for disk IOPS with same priority as more important services such customer downloads/uploads, audits and repairs. The community introduced workarounds to disable the initial used-space calculation on startup by adding the `--storage2.piece-scan-on-startup` flag.

The lazyfilewalker runs the used-space calculation and garbage collection filewalkers as low priority subprocesses. It came up as a solution to the earlier mentioned problems, where these filewalkers run with the same I/O priority as customer downloads.

The complete functionality is available to nodes running on v1.80.0 and later. By default, the lazyfilewalker is disabled, and it can be enabled setting `--pieces.enable-lazy-filewalker=true`.  
We need volunteers to help this this functionality (especially for large nodes running on windows).  
Once enabled, you can check the logs to see if the subprocess runs/completes successfully:

```auto
docker logs storagenode | grep "lazyfilewalker.*.subprocess"

```

---

_[View the full topic](https://forum.storj.io/t/enabling-the-lazyfilewalker/22966)._