Version v1.148.3 is not correctly obtaining the storage capacity specified in the config.yaml

[pcresumen]

Good morning,

About 11 hours ago, one of my nodes automatically updated to v1.148.3, and now its storage capacity has been literally reduced by half. Of the 10TB allocated in the config.yaml file, the dashboard is only showing 5.08TB, which is very strange.

Images attached:

Then I tried something absurd to see what would happen: I took the file and increased the capacity by 500GB to see what would happen. After restarting the node, this is what happened:

It seems absurd to add an extra 5TB just to restore the original capacity…

How can I fix this so it reads the capacity correctly?

[Ollie]

Same thing happened to me! It looks like your browser is stuck on a cached version of the page since those new daily blobs aren’t showing up in the graphs yet. A quick Ctrl + F5 should fix it and pull in the latest update.

Blobs (technical term)

[pcresumen]

Thank you so much @Ollie, it hadn’t even crossed my mind that it was that… although I could swear I had done it, hehe.

[hwm.land]

They changed api, try call /api/sno/
Broke my monstr dashboard project as well

[jammerdan]

@hwm.land

They changed api,

Yes, right:

Before: {"used":0,"available":0,"trash":0,"overused":0}
Now: {"used":0,"available":0,"overused":0,"allocated":0,"trash":0,"reclaimable":0} and allocated seems to be what was available before. And new available seems to be allocated but not used space.