Hello gang. As it was mentioned somewhere else on the forum, the dedicated disk functionality is deprecated. Based on this I did switch back to standard space accounting on nodes that do run hashstore (I do not run piecestore anymore). After the switch some of the nodes are reporting as they are o…

It appears setting the storage2.piece-scan-on-startup: true and then restarting the node fixes the issue. I confirmed this on multiple. Just restarting the node doesn’t fix the problem. I can only assume the node probably was accounting for pieces from the blobs directory which no longer were ther…

I am seeing the same issue on countless nodes all on hashstore. Gotten to the point data has stopped coming in on some nodes, due to false overuse. Resulting in less ingress, and therefor less earnings. Not a fix in miles.

Could you please provide results with this tool: [image] Disk usage discrepancy? troubleshooting Please install stbb from GitHub - elek/stbb · GitHub and run this command (replace the path to yours): stbb hashstore stat /opt/storj/storagenode1765/hashstore/12L…

Yes, if all pieces were migrated, but the databases (they used for piecestore) were not updated, it can explain this.

I’m having this issue and --storage2.piece-scan-on-startup=true doesn’t seem to fix it. Should I remove --pieces.enable-lazy-filewalker=true? I ran the stbb command against one of the nodes but I’m not sure what I should be looking at.

Hello @mattventura , Welcome back! You may leave these options as is. The bloom filters are started to come, but only for AP1 and EU1 yet. If you have a discrepancy between used on the dashboard piechart and your physically used space, perhaps deleting the prefixes database and restart might fix th…

Free space reported incorrectly

Node Operators troubleshooting

Alexey July 25, 2026, 1:16am 3

Could you please provide results with this tool: