# 2 nodes no more ingress

**URL:** <https://forum.storj.io/t/2-nodes-no-more-ingress/29964>\
**Category:** troubleshooting\
**Tags:** multiple-nodes\
**Created:** [May 15, 2025, 2:22am UTC](https://forum.storj.io/t/2-nodes-no-more-ingress/29964 "2025-05-15T02:22:51Z")\
**Posts on this page:** 1\
**Showing post:** 11

<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:** [October 10, 2025, 6:36am UTC](https://forum.storj.io/t/2-nodes-no-more-ingress/29964/11 "2025-10-10T06:36:16Z")

</div>

Hashstore uses a probabilistic model to estimate a used space and calculate a free space in the allocation.  
Similar to suggested there:

> [@On a statistical approach for the used space file walker](https://forum.storj.io/t/on-a-statistical-approach-for-the-used-space-file-walker/27110):
>
> We’ve recently got a [large number of problems that require a full run of a used space file walker](https://forum.storj.io/t/disk-usage-discrepancy/24715), and we have a large number of posts complaining about its duration. We have also seen that its duration is also a source of problems—not all changes to storage while the file walker is running are accounted. One key observation that was made is that the measured values of disk space do not have to be fully accurate, and it should be acceptable to have a decent approximation. This suggests that a s…

Seems the easy fix is to enable a dedicated disk, or use overprovisioning, the node would stop at 5GB of free space on the disk anyway. But it’s an emulation of a dedicated disk in this case, so why to make several hops?

---

_[View the full topic](https://forum.storj.io/t/2-nodes-no-more-ingress/29964)._
