# V58 db migrate fail - piece\_expiration.db - 1.108.3

**URL:** <https://forum.storj.io/t/v58-db-migrate-fail-piece-expiration-db-1-108-3/27238>\
**Category:** troubleshooting\
**Tags:** database\
**Created:** [July 23, 2024, 6:13am UTC](https://forum.storj.io/t/v58-db-migrate-fail-piece-expiration-db-1-108-3/27238 "2024-07-23T06:13:30Z")\
**Posts on this page:** 1\
**Showing post:** 45

<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:** [July 30, 2024, 8:43am UTC](https://forum.storj.io/t/v58-db-migrate-fail-piece-expiration-db-1-108-3/27238/45 "2024-07-30T08:43:43Z")

</div>

> [@V1.107.3 as "minimum" on https://version.storj.io](https://forum.storj.io/t/v1-107-3-as-minimum-on-https-version-storj-io/27338/14):
>
> Looks like v1.108.3 is now minimum. Now that collector properly updates the deleted pieces after a run of used-space we should see far less disk usage discrepancy reports on the forum. Interesting this is not the case for me.

---

_[View the full topic](https://forum.storj.io/t/v58-db-migrate-fail-piece-expiration-db-1-108-3/27238)._