Hi guys,
I have recently stumbled across an interesting issue.
I have an older node that I wanted to upgrade as the allocated space is full. I had this set to around 11TB than changed that to 12TB all went well and slowly the node filled up. Now I want to expand it to like 13-14TB.
I opened the file “config.yml” file and changed it from 12.00 to 13.00
After service restart (yes running it on windows)
The dashboard says 12TB, yes I cleared the cache and even tried a different browser. also muntinode dashboard also sees it as 12TB
Have you checked that you havent set the capacity to 12TB in an environmental variable or as a launch parameter? These two will have priority over the value at the config.yaml file.
It looks like the windows installer creates a startup command with the space available set in it
ExeCommand=" … --storage.allocated-disk-space "[STORJ_STORAGE] …
I’m rooting around in their source without really knowing much about windows but maybe you set it?
2 things you could check:
1.) edit config.yaml as admin (Notepad++ will give you a warning if it can’t save due to lack of admin rights, for example).
2.) From the Services app, stop the node and start it again (different from “restart”).
You can also check the log if the correct config is loaded, as these are printed to the log on each startup. When on Windows the config.yaml file should be enough in order to change the storage used.
If you really want to be sure, you could also right-click on the storagenode.exe file (as used in the Services app) and check if any parameters are set there (under Properties).
I checked the config using powershell, and yes it is saved:
C:\Program Files\Storj\Storage Node\config.yaml:130:# file preallocated for uploading
C:\Program Files\Storj\Storage Node\config.yaml:172:# total allocated bandwidth in bytes (deprecated)
C:\Program Files\Storj\Storage Node\config.yaml:173:storage.allocated-bandwidth: 0 B
C:\Program Files\Storj\Storage Node\config.yaml:175:# total allocated disk space in bytes
C:\Program Files\Storj\Storage Node\config.yaml:176:storage.allocated-disk-space: 13.00 TB
Also I stopped and started the service still no luck, I even restarted the server for good measure.
Than I also searched the log for “less than allocated” But without luck.
Nothing seems to be wrong with the logs.
Hey So I searched that term the whole phrase and also used the key words “less” “requested” and “allocated” none of the terms show up in the logs
I will attempt to reinstall the node later today. I need to do some prep for that
Thanks for the suggestions, I got a possibly stupid question, I just happned to do a similar upgrade on a different node, and a similar thing happened to me at 10.99Tb when I set it to 11.50Tb
Could it be that Storj is looking at the maximum capacity of the drive that windows is reporting and using that as some sort of CAP?