# Unknown flag: --storage2.piece-scan-on-startup

**URL:** <https://forum.storj.io/t/unknown-flag-storage2-piece-scan-on-startup/23017>\
**Category:** troubleshooting\
**Tags:** docker\
**Created:** [June 20, 2023, 6:04am UTC](https://forum.storj.io/t/unknown-flag-storage2-piece-scan-on-startup/23017 "2023-06-20T06:04:09Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![nerdatwork](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/nerdatwork/32/1135_2.png) [@nerdatwork](https://forum.storj.io/u/nerdatwork)\
**Post date:** [June 20, 2023, 6:20am UTC](https://forum.storj.io/t/unknown-flag-storage2-piece-scan-on-startup/23017/2 "2023-06-20T06:20:11Z")

</div>

> [@Enabling the Lazyfilewalker](https://forum.storj.io/t/enabling-the-lazyfilewalker/22966):
>
> 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 filew…

---

_[View the full topic](https://forum.storj.io/t/unknown-flag-storage2-piece-scan-on-startup/23017)._
