# Release preparation v1.113

**URL:** <https://forum.storj.io/t/release-preparation-v1-113/27872>\
**Category:** STORJLINGS\
**Created:** [September 13, 2024, 3:50pm UTC](https://forum.storj.io/t/release-preparation-v1-113/27872 "2024-09-13T15:50:56Z")\
**Posts on this page:** 16\
**Page:** 3

<div class="post-metadata">

**Author:** ![Mitsos](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/mitsos/32/1125_2.png) [@Mitsos](https://forum.storj.io/u/Mitsos)\
**Post date:** [September 25, 2024, 5:41pm UTC](https://forum.storj.io/t/release-preparation-v1-113/27872/41 "2024-09-25T17:41:49Z")

</div>

I don’t see any config change in 1.114rc to enable this new space feature.

---

<div class="post-metadata">

**Author:** ![arrogantrabbit](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/arrogantrabbit/32/11200_2.png) [@arrogantrabbit](https://forum.storj.io/u/arrogantrabbit)\
**Post date:** [September 25, 2024, 6:19pm UTC](https://forum.storj.io/t/release-preparation-v1-113/27872/42 "2024-09-25T18:19:00Z")

</div>

> [@Roxor](#):
>
> If it shows you a number for “used space”… but it didn’t actually add up all the .sj1 files (like it does now)… it wouldn’t be a real number, would it?

of course it would, by definition – that’s what the used space is, what filesystem reports it to be.

> [@Roxor](#):
>
> It’s at best an educated guess.

I’d argue adding up the sj1 files is an educated guess (among other reasons – while you are done adding up last file, first few could have been deleted and a few more added). Asking filesystem how much free space is there or how much is used – is the atomic source of truth.

---

<div class="post-metadata">

**Author:** ![Roxor](https://storj.bcdn.literatehosting.com/letter_avatar/roxor/32/5_5575768a8748004e209b776fc1b2916d.png) [@Roxor](https://forum.storj.io/u/Roxor)\
**Post date:** [September 25, 2024, 6:37pm UTC](https://forum.storj.io/t/release-preparation-v1-113/27872/43 "2024-09-25T18:37:01Z")

</div>

> [@arrogantrabbit](#):
>
> Asking filesystem how much free space is there or how much is used – is the atomic source of truth.

Asking a filesystem how much space is free… _tells you nothing_ about how much the Storj node is using. It could be 90% cat videos, and 1% .sj1’s. Which is why Storj’s used-space today is calculated by adding up the blobs. This enhancement allows a node to assume it’s the only user-of-space… so subtracting free-space from total-space should be very close to storj-used-space.

It’s a useful upgrade, and I’m sure many SNOs will enable it. But it’s useless on mixed-use filesystems.

---

<div class="post-metadata">

**Author:** ![arrogantrabbit](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/arrogantrabbit/32/11200_2.png) [@arrogantrabbit](https://forum.storj.io/u/arrogantrabbit)\
**Post date:** [September 25, 2024, 6:52pm UTC](https://forum.storj.io/t/release-preparation-v1-113/27872/44 "2024-09-25T18:52:57Z")

</div>

No, the discussion is already in the context of the node having exclusive use of the disk. There are no cat videos.

Full quote:

> This patch identifies the available space in a different way. It ignores all the calculated used space, but checks the available space in the running partition. UI will show fake numbers, but it should work."

Hence, the last statement in this quote is wrong. If anything, the number will become more accurate.

---

<div class="post-metadata">

**Author:** ![Roxor](https://storj.bcdn.literatehosting.com/letter_avatar/roxor/32/5_5575768a8748004e209b776fc1b2916d.png) [@Roxor](https://forum.storj.io/u/Roxor)\
**Post date:** [September 25, 2024, 6:57pm UTC](https://forum.storj.io/t/release-preparation-v1-113/27872/45 "2024-09-25T18:57:08Z")

</div>

> [@arrogantrabbit](#):
>
> Hence, the last statement in this quote is wrong. If anything, the number will become more accurate.

This enhancement tells the node to _assume_ it’s the only thing using the disk. It’s not making all other directories on the filesystem read-only or anything. You drop one .txt file anywhere on that drive and the used-by-storj number is incorrect. I believe that’s what they mean by “fake”… because the node isn’t actually checking. It’s hoping.

---

<div class="post-metadata">

**Author:** ![arrogantrabbit](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/arrogantrabbit/32/11200_2.png) [@arrogantrabbit](https://forum.storj.io/u/arrogantrabbit)\
**Post date:** [September 25, 2024, 7:03pm UTC](https://forum.storj.io/t/release-preparation-v1-113/27872/46 "2024-09-25T19:03:01Z")

</div>

Ok, but the numbers will be fake only if user breaks the promise of exclusive use. I’ll just assume it’s a poor choice of words.

---

<div class="post-metadata">

**Author:** ![Aleksman4o](https://storj.bcdn.literatehosting.com/letter_avatar/aleksman4o/32/5_5575768a8748004e209b776fc1b2916d.png) [@Aleksman4o](https://forum.storj.io/u/Aleksman4o)\
**Post date:** [September 25, 2024, 7:16pm UTC](https://forum.storj.io/t/release-preparation-v1-113/27872/47 "2024-09-25T19:16:21Z")

</div>

I haven’t promised exclusive use. Hey, there 14TB, which will be used by storj in about 2 years (it’s very optimistic). Why that’s empty space shouldn’t be used by my cat video?

---

<div class="post-metadata">

**Author:** ![Roxor](https://storj.bcdn.literatehosting.com/letter_avatar/roxor/32/5_5575768a8748004e209b776fc1b2916d.png) [@Roxor](https://forum.storj.io/u/Roxor)\
**Post date:** [September 25, 2024, 7:24pm UTC](https://forum.storj.io/t/release-preparation-v1-113/27872/48 "2024-09-25T19:24:46Z")

</div>

> [@Aleksman4o](#):
>
> …which will be used by storj in about 2 years…

Off-topic: Do you have a feel for how fast you think your node is filling a disk? Some people are collecting estimates [here](https://forum.storj.io/t/node-fill-status-poll-older-than-12-months/28045) so we can all compare.

---

<div class="post-metadata">

**Author:** ![Mitsos](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/mitsos/32/1125_2.png) [@Mitsos](https://forum.storj.io/u/Mitsos)\
**Post date:** [September 25, 2024, 8:05pm UTC](https://forum.storj.io/t/release-preparation-v1-113/27872/49 "2024-09-25T20:05:41Z")

</div>

> [@Aleksman4o](#):
>
> **I haven’t promised exclusive use.** Hey, there 14TB, which will be used by storj in about 2 years (it’s very optimistic). Why that’s empty space shouldn’t be used by my cat video?

I have. As a tradeoff, I don’t have to deal with running used-space filewalker (in 2 years when that drive fills up, you’ll see it take a couple of weeks to get through used-space filewalker, per run). The drive is dedicated to storj, and storj alone. The only metric I care for the node to keep track of is the free space (which in theory it should do every 10 mins, based on what the OS is reporting = instantly). Once per restart, the trash folder gets scanned for the space it occupies.

That leaves us with how much space is actually used by the node (park the “fake” space reports aside and the per satellite usage, I don’t care). Used space (for dashboard display) = max drive size (as reported by OS) - trash (see above) - free space (as reported by OS) - space reserved (set by me in config.yaml). Quintillions of IOPS saved = happy SNOs = happy clients = Storj can claim even smaller carbon footprint = win-win situation.

Looking forward to that single reply “but the most important piece of information in modern world is the per satellite usage, I cannot get through my day without knowing this extremely important detail!!!11oneeleven”.

TL;DR: Some people are willing to trade space for convenience. This change is exclusively for them.

---

<div class="post-metadata">

**Author:** ![Aleksman4o](https://storj.bcdn.literatehosting.com/letter_avatar/aleksman4o/32/5_5575768a8748004e209b776fc1b2916d.png) [@Aleksman4o](https://forum.storj.io/u/Aleksman4o)\
**Post date:** [September 25, 2024, 8:16pm UTC](https://forum.storj.io/t/release-preparation-v1-113/27872/50 "2024-09-25T20:16:28Z")

</div>

> [@Mitsos](#):
>
> you’ll see it take a couple of weeks to get through used-space filewalker, per run

my 4TB node doing it for ~1.5 hours

---

<div class="post-metadata">

**Author:** ![Mitsos](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/mitsos/32/1125_2.png) [@Mitsos](https://forum.storj.io/u/Mitsos)\
**Post date:** [September 25, 2024, 8:22pm UTC](https://forum.storj.io/t/release-preparation-v1-113/27872/51 "2024-09-25T20:22:08Z")

</div>

> [@Aleksman4o](#):
>
> my 4TB node doing it for ~1.5 hours

The “method of three” does not apply in storj nodes, as I have said numerous times in the past. You can’t extrapolate that a 14TB node will take 5 hours for a used-space.

Can’t comment on badger, I don’t plan to enable it any time soon.

---

<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:** [September 26, 2024, 7:54am UTC](https://forum.storj.io/t/release-preparation-v1-113/27872/52 "2024-09-26T07:54:29Z")

</div>

For me it looks like an equivalent of `df`.

> [@arrogantrabbit](#):
>
> Why would then UI show fake numbers?

because it doesn’t include any change for the UI, so the UI will still use a DB.

---

<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:** [September 26, 2024, 7:58am UTC](https://forum.storj.io/t/release-preparation-v1-113/27872/53 "2024-09-26T07:58:36Z")

</div>

In that case you are in my shoes, you will not enable this feature and would relay on a used-space-filewalker, and that all updates of the databases are finished without any issues.

---

<div class="post-metadata">

**Author:** ![pasatmalo](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/pasatmalo/32/1127_2.png) [@pasatmalo](https://forum.storj.io/u/pasatmalo)\
**Post date:** [September 26, 2024, 8:38am UTC](https://forum.storj.io/t/release-preparation-v1-113/27872/54 "2024-09-26T08:38:26Z")

</div>

> [@arrogantrabbit](#):
>
> Also, this mechanism is already used to prevent running out of space (the 3GB buffer or whatever it is today)

Im not 100% sure, but I believe right now the 5GB buffer when ingress is halted actually depends on the used space calculations and not the actual available space. Therefore, if the used space calculation is wrong (as it tends to be sometimes), then it may actually use the last 5GB buffer instead of stopping ingress.

---

<div class="post-metadata">

**Author:** ![arrogantrabbit](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/arrogantrabbit/32/11200_2.png) [@arrogantrabbit](https://forum.storj.io/u/arrogantrabbit)\
**Post date:** [September 26, 2024, 5:28pm UTC](https://forum.storj.io/t/release-preparation-v1-113/27872/55 "2024-09-26T17:28:57Z")

</div>

No, the whole point of that check is to avoid filling the disk if the used space calculation is not accurate.

In fact, I have set node allocation size to 200TB, and then applied a quota on a dataset to the actual size I want node to be limited to. This works correctly.

---

<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:** [September 27, 2024, 4:53am UTC](https://forum.storj.io/t/release-preparation-v1-113/27872/56 "2024-09-27T04:53:53Z")

</div>

> [@pasatmalo](#):
>
> but I believe right now the 5GB buffer when ingress is halted actually depends on the used space calculations and not the actual available space.

It checks a minimum available space from both values, either of them will trigger a “node is full” signal.

[Previous page](https://forum.storj.io/t/release-preparation-v1-113/27872.md?page=2)
