# Free space reported incorrectly

**URL:** <https://forum.storj.io/t/free-space-reported-incorrectly/32051>\
**Category:** troubleshooting\
**Tags:** storage, database, hashstore\
**Created:** [July 24, 2026, 10:38am UTC](https://forum.storj.io/t/free-space-reported-incorrectly/32051 "2026-07-24T10:38:37Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![zip](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/zip/32/7813_2.png) [@zip](https://forum.storj.io/u/zip)\
**Post date:** [July 27, 2026, 8:26pm UTC](https://forum.storj.io/t/free-space-reported-incorrectly/32051/4 "2026-07-27T20:26:21Z")

</div>

It appears setting the `storage2.piece-scan-on-startup: true` and then restarting the node fixes the issue. I confirmed this on multiple.  
Just restarting the node doesn’t fix the problem.  
I can only assume the node probably was accounting for pieces from the blobs directory which no longer were there, and startup scan flushed those bytes away.

---

_[View the full topic](https://forum.storj.io/t/free-space-reported-incorrectly/32051)._