After a system crash storage usage is incorrect

[Meowcat285]

My NAS that I run my storage node on crashed earlier and now my total storage usage is significantly down. Previously I was using about 50 GB or so, but now it’s down to 12 GB (brand new node BTW.) Is this any cause for concern? If it is how do I fix it?

[Meowcat285]

I just checked the storj directory usage and its 66GB, but the storage node UI is only showing 12 GB

[Meowcat285]

I tried restarting the node and now it shows 10 GB, but the storj directory is still 66 GB and the blobs directory is 65 GB

[Meowcat285]

Even weirder, according to /app/dashboard.sh my usage is 10 GB, but with about 458 GB available, while the web UI reports 0.99 TB total and 0.98 TB free

[Meowcat285]

Ah, I fixed this by recreating most of the databases that have to do with storage usage following this guide: https://support.storj.io/hc/en-us/articles/4403032417044-How-to-fix-database-file-is-not-a-database-error

[Alexey]

Perhaps only this one might be enough:

@Alexey

• Stop and remove the container (or stop the service, if you use a service based setup)
• Rename the used_space_per_prefix.db database to used_space_per_prefix.db.bak
• Move all databases (*.db) to the temp folder
• Start the node, wait until it would re-create all databases
• Stop the node
• Move databases from the temp folder back to the storage location with replace
• Start the node
• Wait until all used-space-filewalkers will finish the scan without issues (no database or filewalker errors)
• Check the dashboard