Used_serial.db malformed

[Alexey]

@ianllew600

Is revocations.db able to be fixed?

Please stop storagenode, rename this database and start the storagenode back.

@ianllew600

usedserialsdb error: database is locked

Database is locked. What is the reason? What is the possible solution?

Short update from a meeting with the developers today about the db locking: The piece size is way too small and causing an IOPS bottleneck that we need to fix. I am not sure about the details but the long term goal is to write bigger pieces to disk. That should improve performance. Why do we store serial numbers for 48h in a DB? We should keep that in memory and don’t write it to disk at all. That will solve that problem entirely. We still want to write orders into a DB. If the node is restart…

and it’s fixed in the next version. At the moment can help only vacuuming:

"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 "…