Node Thrashing Disk all the time

[Alexey]

Yes, the vacuum could help sometimes, but it contains a bandwidth history, see

"Action": "GET_AUDIT", "error": "usedserialsdb error: database is locked",

I’m running a docker version on Debian GNU/Linux. Here’s the procedure I use to vacuum and check the databases: Stop the node Vacuum the dbs integrity_check the dbs Restart the node Here’s a bash check which should do that for you. Please change the database directory to reflect where yours are on your system. docker stop -t 300 storagenode && dbs=$(ls /opt/storj/storage/*.db) c1="VACUUM;" c2="PRAGMA integrity_check;" for i in $dbs do sqlite3 $i "$c1" done for i in $dbs do sqlite3 $i "…

And read also

Is the vacuum necessary?

I cannot help but wonder if vaccuming the database is a good or a bad thing… people on here has been talking about that a lot lately, most sort of just go… oh look at this thing… and then i do this and it’s smaller after i’m done… and on harddrives smaller is better… so must be right… vacuuming is better… i don’t really know a lot about database management, i’ve worked with a few here and there…pretty simple stuff at first… you and like rows and columns of information, that you basically can se…

Yes, you may re-create it using the instruction https://support.storj.io/hc/en-us/articles/4403032417044-How-to-fix-database-file-is-not-a-database-error, but the usage history will be lost.