Bug in 1.152.5 - disk size

Node Operators troubleshooting
,
1

My nodes updated now to v 1.152.5 and did not started.

2026-04-23T20:04:36Z    WARN    Disk space is less than requested. Allocated space is   {"process": "storagenode", "bytes": 352777011200}
2026-04-23T20:04:36Z    ERROR   Total disk space is less than required minimum  {"process": "storagenode", "bytes": 500000000000}

Node has 2TB set in configuration, it’s 2TB dataset on zfs. Reported amount 352777011200 was free space on this dataset. I have free space on this pool, so I increased quota by 200GB and node started. I suppose there could be quite a lot surprissed node operators with nodes close to disk capacity!

2

5 nodes have updated to 1.152.5

constantly restarting saying it doesnt have enough space

3

yep - i’m seeing this … just now

4

I also just updated two nodes, both had 2.7TB-3TB of free space. After restarting it showed 5TB+ overuse, so incoming traffic stopped.

5

yes… it is complaining about not having 500gigs free space… and that is true in my case… but i want it that way.

edit your config.yaml and change this : # storage2.monitor.minimum-disk-space: 500.00 GB
to:
storage2.monitor.minimum-disk-space: 250.00 GB

and that is the amount of disk space i want to keep free on this specific server.

6

dedicated disk mode , i believe works on theory of 100GB

@Alexey are you aware?

7

i do not run this specific node in dedicated disk mode though. soo???

8

ah ok , yeah my nodes all run like this

9

Maybe make a github bug report?

10

hi team,

how can i roll the version back ??

11

Having a small node on a 1TB drive, configured with 900GB for Storj. This node is also constantly failing and restarting. Logs say as well:
2026-04-23T21:07:58Z ERROR Total disk space is less than required minimum {“process”: “storagenode”, “bytes”: 500000000000}

12

I think one way is to change the version url in config to something wrong and then replace the binary in the storagenode location with the older one from github.

13

Two nodes down here because of this.

14

I would recommend to use dedicated disk until the bug is fixed. It seems they have tested this release only on select… :wink:

15

i am not sure if that config.yaml change does work then. maybe you can try this?

16

Hello,
I just got a similar problem with this version

17

I am using dedicated disk , - doesn’t work unfortunately - doesnt seem to be listening to the 100G rule i have

18

I had this too. But those two who failed like this are still on 1.148.3?
I was able to fix this by removing the docker and recreating it.
But it only affected both nodes with full drives.

19

Hello, do you use it with docker ?
If yes, can you past how you do that ?

20

hi

i run via , ‘docker run’

i use this variable - , at end of the docker run

–storage2.monitor.minimum-disk-space=“10GB” \

has got it back online… however it is not a good setting to have to play around with