# Understanding the node space calculation (not)

**URL:** <https://forum.storj.io/t/understanding-the-node-space-calculation-not/32983>\
**Category:** troubleshooting\
**Tags:** hashstore, used-space\
**Created:** [October 28, 2026, 6:27am UTC](https://forum.storj.io/t/understanding-the-node-space-calculation-not/32983 "2026-10-28T06:27:19Z")\
**Posts on this page:** 8\
**Page:** 2

<div class="post-metadata">

**Author:** ![snorkel](https://storj.bcdn.literatehosting.com/letter_avatar/snorkel/32/6_449c533f586939b6e5f246632a46421f.png) [@snorkel](https://forum.storj.io/u/snorkel)\
**Post date:** [October 31, 2026, 9:54am UTC](https://forum.storj.io/t/understanding-the-node-space-calculation-not/32983/21 "2026-10-31T09:54:51Z")

</div>

Did you stop node and delete databases? It usualy helps.

---

<div class="post-metadata">

**Author:** ![jammerdan](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/jammerdan/32/1121_2.png) [@jammerdan](https://forum.storj.io/u/jammerdan)\
**Post date:** [October 31, 2026, 3:05pm UTC](https://forum.storj.io/t/understanding-the-node-space-calculation-not/32983/22 "2026-10-31T15:05:09Z")

</div>

That’s an interesting suggestion. No I have not yet tried that.

---

<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:** [November 1, 2026, 12:22am UTC](https://forum.storj.io/t/understanding-the-node-space-calculation-not/32983/23 "2026-11-01T00:22:25Z")

</div>

As explained above, it reserves this space for compaction. I don’t know your configuration options for hashstore, but might guess that you configured it to be aggressive to have less reclaimable space. So the node expects to have a free space to make it.

Please show, how much reclaimable space it contains?

I wonder what would happen after the compaction will be done?

---

<div class="post-metadata">

**Author:** ![jammerdan](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/jammerdan/32/1121_2.png) [@jammerdan](https://forum.storj.io/u/jammerdan)\
**Post date:** [November 1, 2026, 4:08am UTC](https://forum.storj.io/t/understanding-the-node-space-calculation-not/32983/24 "2026-11-01T04:08:29Z")

</div>

> [@Alexey](#):
>
> it reserves this space for compaction

If that’s the case then it explains what I am saying in other words: The node occupies space (in my case 1.3TB?) that cannot be used for uploads. Thereofere it is unpaid occupied space like trash.

Still I don’t get it why the node believes it requires 1.3TB for compaction at allocated space of 5.5TB and zero at allocation of 5.6TB?

I mean the “fix” is easy: Add at least 100GB to the allocation and the node gets ingress again. But for me it does not seem logical what the node is doing.

> [@Alexey](#):
>
> Please show, how much reclaimable space it contains?

 ![Screenshot_2026-11-01_050452](https://storj-s3.bcdn.literatehosting.net/original/3X/7/f/7f6d4cfff391e69b598a4591b270966c0c3df813.jpeg)

I am running the node with allocated 6TB currently to be safe that it does not get cut off from ingress again.

---

<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:** [November 1, 2026, 8:11am UTC](https://forum.storj.io/t/understanding-the-node-space-calculation-not/32983/25 "2026-11-01T08:11:38Z")

</div>

> [@jammerdan](#):
>
> Still I don’t get it why the node believes it requires 1.3TB for compaction at allocated space of 5.5TB and zero at allocation of 5.6TB?

I think it still wants to have 1.3TB, but while it has more, it doesn’t block it.  
However, I want to get a confirmation from the team that’s expected behavior.

---

<div class="post-metadata">

**Author:** ![Julio](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/julio/32/1132_2.png) [@Julio](https://forum.storj.io/u/Julio)\
**Post date:** [November 5, 2026, 2:33am UTC](https://forum.storj.io/t/understanding-the-node-space-calculation-not/32983/26 "2026-11-05T02:33:18Z")

</div>

Could it be a leftover from an incomplete piecestore count in the database, lurking since your transition to hashstore?  
activate your flags, if they were off.

storage2.piece-scan-on-startup  
pieces.enable-lazy-filewalker

1.55 cents,

Julio

---

<div class="post-metadata">

**Author:** ![snorkel](https://storj.bcdn.literatehosting.com/letter_avatar/snorkel/32/6_449c533f586939b6e5f246632a46421f.png) [@snorkel](https://forum.storj.io/u/snorkel)\
**Post date:** [November 5, 2026, 4:31am UTC](https://forum.storj.io/t/understanding-the-node-space-calculation-not/32983/27 "2026-11-05T04:31:25Z")

</div>

The lazy mode should stay off. It created all sorts of problems. And it is not needed anymore with hashstore. I sugest removing the code along with the piecestore part, when time comes.

---

<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:** [November 5, 2026, 4:36am UTC](https://forum.storj.io/t/understanding-the-node-space-calculation-not/32983/28 "2026-11-05T04:36:07Z")

</div>

That’s the plan. When all nodes will migrate to hashstore we plan to remove the piecestore related code.

[Previous page](https://forum.storj.io/t/understanding-the-node-space-calculation-not/32983.md?page=1)
