Quote:
Originally Posted by jbaumann
I'm not sure what KSM does (or the file monitor) that corrupts the database, but it definitely does something.
@tshering: How can I determine what happens in more detail? I'm willing to experiment to some extent, because I would very much like to have the ability to choose koreader (for PDF reflow) and Coolreader (simply because I can) for my reading experience :-)
|
Quote:
Originally Posted by jbaumann
What I did:
...
- Copied 100 books to the reader with calibre
- Database was ok after copying
- Unplugged and waited for the reader to finish processing the books
- Plugged it in again and lo and behold, the database was corrupted
|
Difficult to say what is happening here. At this point, apart from the original kobo stuff, only fmon and two or three shell scripts are running (the scripts do basically nothing but waiting that nickel exits, so that the KSM application can be started again.)
I was first thinking that there might be situations that nickel gets killed (when choosing exit_nickel.png), before it has finished writing to the database. At least in your 4 steps above, this seems however not to be the case.
As for sqlite3, there is an executable included in KSM (.adds\kbmenu\tools\sqlite3). You can do a simple integrity check of the database by selecting tools > kobo diverse.msh > db chk integrity.sh. For the above described situation this will however not help you (since nickel is running at that point). So you would have to do it with telnet via wifi (you might need to look around in this forum on how to prevent nickel from disconnecting the wifi connection).
Maybe I should mention that I was using KSM since it was available. I never had any problems with the database since then (except by my own fault when experimenting). But I am not a good test case, because I never use caliber to put books on the reader. So maybe it is somehow the combination of using KSM and calibre. But I have no idea of what exactly could be the cause of the corruption.
Edit: By the way, you can start nickel from KSM via tools > kobo diverse.msh > start nickel no fmon.sh. In this case fmon will not be involved at all. (You will have to power off by using the power button, there is no way to get back from nickel to KSM in this situation.