# Database locking madness

**URL:** <https://forum.storj.io/t/database-locking-madness/26026>\
**Category:** troubleshooting\
**Tags:** hardware, database\
**Created:** [April 30, 2024, 7:02am UTC](https://forum.storj.io/t/database-locking-madness/26026 "2024-04-30T07:02:36Z")\
**Posts on this page:** 1\
**Showing post:** 15

<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:** [May 5, 2024, 7:38am UTC](https://forum.storj.io/t/database-locking-madness/26026/15 "2024-05-05T07:38:57Z")

</div>

> [@Qwinn](#):
>
> I have seen some posts by people saying that filewalker doesn’t really need to be run more than once a year? Is that really true?

It can be true for the `used-space-filewalker`, if you did not have a discrepancy in the used and showed as used before and if you do not have a side load (Chia mining, your own usage, etc.) on the same disk.

> [@Qwinn](#):
>
> Could it at least be set to only trigger a filewalker run if the node was restarted _manually_, and not for a version update?

Yes. Set this option to true (or remove it):

> [@Filewalker status](https://forum.storj.io/t/filewalker-status/25325/20):
>
> `--storage2.piece-scan-on-startup=false`

If you use a `config.yaml`, this option would be

```auto
storage2.piece-scan-on-startup: false

```

so you need either set it to `true` or comment out, save the config and restart the node.

---

_[View the full topic](https://forum.storj.io/t/database-locking-madness/26026)._
