View Single Post
Old 10-06-2015, 06:58 PM   #995
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
As PeterT said, the database is corrupt. The backup process copies the database to the local drive and then runs a check on it to make sure it is OK. If it isn't OK, you will get an error something like you are seeing (which I really should add some more explanation top). When this happens, the backed up file is renamed to include the word "CORRUPT".

Because of what is corrupt, an autoindex on the Event table, you probably won't notice any problems. If anything goes wrong, it will be something like not keeping the reading stats properly. And when you connect and sync books with calibre, it won't complain as the table with the error is not one the driver uses. Luckily, this type of error can usually be fixed. If you use the utilities plugin function to do a compress (really an SQLite VACUUM), it should rebuild the index.

My suggestion is:
- Check when the last successful backup was.
- Run the compress.
- Run a database check.
- If there are no errors, eject the device and restart the device.
- If there are errors, restore the last successful backup.

That should clear the error when the backup is done.
davidfor is offline