Quote:
Originally Posted by JSWolf
Since I'm not going to read back in this thread, are you running calibre from the official calibre site or are you running calibre from a repository?
|
Originally, I was just running this locally. I had a backup script I would run every 12 weeks or so, that would automatically create a date-named folder, perform the export, and run a hash against all the files. One day, this just stopped working. This thread was my attempt at trying to figure out what could be causing this issue.
I've tried sandboxing the environment, running a debug instance, all of them failed at the same place during the export. I decided, let me try a "clean" environment and run calibre command-line entirely within the container, and just map the external volume into the container. It failed at the same spot - backing up the metadata.db file.
Quote:
Originally Posted by kovidgoyal
No size is irrelevant. As for repairing, you can always dump it to sqlite and rebuild from that, or use calibredb restore_database to rebuild it completely from OPF files, but read the help of that command to see its limitations.
|
Before I run this command, I'll backup the metadata.db file. I also clicked on Calibre Library>Library Maintenance>Check Library and the results came back that everything is good. So, I'm not sure that doing a restore_database will solve this issue.