New release v1.153 is already deployed on QA Satellite Here is a list of changes: Changelog General a2c647b cmd/tools/om-license: new tool to grant OM licenses to active users 5528a6c all: use atomic types where possible d6b15df all: use reflect.TypeFor instead of reflect.TypeOf 22ce77e all: …

[image] Bug in 1.152.5 - disk size troubleshooting upgraded one of nodes today to v1.153.2 (windoze) , and my allocated space went from 9tb to 6,08tb , issue is still ongoing with latest version

Perhaps not related, need more data. It could be usual not finished filewalker, so the node didn’t recognize part of the used space and used a minimum between the actual available space and allocated on start.

i think it is related , had no issues before , just came up after upgrading to 1.153.2 [image] [image] [image] other node that runs 1.152.3 works as it suppose to [image]

Having the same issue 152.5 did with 153.2 on docker node. It isn’t listening to my allocated parameter of 13TB, only using 7.61TB, no free space for ingress.

I would suggest to use the recommended version on https://version.storj.io at the moment. @Morisey thank you for notifying. How is it happened, that your node is updated to the not recommended version? The updater shouldn’t do this, or there is a bug.

well since those are kind of shifty boxes i dont use autoupdater , i start services manually and also doing updates manually , so that part is on me , i periodically taking latests from git and updating not to fall behind , so no blame on your part for that , it just that latest versions came out gl…

I see, anyway, thank you for notifying. I shared this issue with the team.

Regarding log space preallocation, I wonder how is the performance impact of it? I know that when I used preallocation for torrent downloads, the client froze for some seconds. I wonder if isn’t better to preallocate all the allocated space for logs, because the size is the same for all. It could be…

I’d like to see some numbers myself. Preallocation makes sense for a random writes, sequential reads scenario. Torrents are a perfect example. But here we have sequential writes. I wouldn’t really see preallocation making any difference, actually I would expect that long-term we should be seeing sli…

Release preparation v1.153

Product Discussions STORJLINGS

Roberto May 5, 2026, 6:40pm 2