Alexey
July 25, 2024, 6:53am
73
Please note, this version has a databases migration, and it could take a few hours (even on SSD) to migrate. Please, do not kill your node during the process, otherwise you may end with a malformed database.
It’s a super old Crucial m4 120GB ssd from 2013. Here are my logs:
2024-07-02T22:42:17Z INFO db.migration.58 Remove unused trash column {"Process": "storagenode"}
2024-07-02T22:43:28Z INFO db.migration.59 Remove unused deletion_failed_at column {"Process": "storagenode"}
2024-07-02T22:44:51Z INFO db.migration.60 Overhaul piece_expirations {"Process": "storagenode"}
2024-07-02T22:46:26Z INFO db.migration Database Version {"Process": "storagenode", "version": 60}
This is running on ZFS with comp…
And the result of killing of the “hanging” node could be like that:
Hello,
Out of the blue my storj container stopped working. I tried restarting it, without success, then I stopped it, deleted the container and redeployed it, also without success. My node was working fine, without any problems, but all of a sudden, this happened. I hope somebody could help me out to minimize my downtime. TiA
Docker-Log:
Error: Error migrating tables for database on storagenode: migrate: v60: database disk image is malformed
storj.io/storj/private/migrate.(*Migration).Run:21…