# Bug in 1.152.5 - disk size

**URL:** <https://forum.storj.io/t/bug-in-1-152-5-disk-size/31716>\
**Category:** troubleshooting\
**Tags:** docker, zfs\
**Created:** [April 23, 2026, 8:19pm UTC](https://forum.storj.io/t/bug-in-1-152-5-disk-size/31716 "2026-04-23T20:19:24Z")\
**Posts on this page:** 1\
**Showing post:** 96

<div class="post-metadata">

**Author:** ![Roxor](https://storj.bcdn.literatehosting.com/letter_avatar/roxor/32/6_449c533f586939b6e5f246632a46421f.png) [@Roxor](https://forum.storj.io/u/Roxor)\
**Post date:** [May 28, 2026, 9:28pm UTC](https://forum.storj.io/t/bug-in-1-152-5-disk-size/31716/96 "2026-05-28T21:28:27Z")

</div>

> [@Vadim](#):
>
> Is there any solution to broken logs that can’t be reclamed?

I wonder if that’s what the [recent lost piece amnesty](https://forum.storj.io/t/hashstore-rollout-commencing/30589/8) feature will be used for? It sounds ideal for repairing/replacing hashstore data logs that can’t be compacted due to corruption.

---

_[View the full topic](https://forum.storj.io/t/bug-in-1-152-5-disk-size/31716)._
