Quote:
Originally Posted by rashkae
I have just made a very interesting observation about firmware 4.31 that I think can explain the issues people have been reporting. I connected my Kobo to my Linux computer and navigated to the .kobo folder very soon thereafter in my desktop file browser. I saw some temporary sqlite files appear in the file list, then disappear without my doing anything. My only conclusion here, the Kobo had not finished unmounting the user partition before allowing the computer to mount it.
Edit: That might not be the whole story, hoiwever. I can see the same thing happening after revering to 4.30,, but at least now I don't have to re-boot the kobo for the database to update properly again.
Edit 2: I had Calibre open. That was responsible for creating then deleting the temp files as part of it'sscanning books on device. Sorry for the noise.
|
Quote:
Originally Posted by frostschutz
It's possible, it happened before.
Kobo uses lazy umounting, and "lazy" means it's not unmounted at all while still in use.
The result is filesystem inconsistency and perhaps includes Windows complaining about the filesystem.
I had a mod to detect this condition ( https://www.mobileread.com/forums/sh...d.php?t=263674 to display a happy or sad smiley face depending on umount status ) and try to detect the cause what is preventing the umount, but of course it's old and unmaintained and probably won't work, for current devices.
Back then it was the KEPUB Reader that prevented umount if you connected while reading the book, it was fine if you connected USB from the home menu.
Of course any addon can also block it, if it has anything in /mnt/onboard open. |
I wonder if that could also explain the database instability I had? If the database wasn't properly closed, I could see how that might result in it getting malformed (or at the very least data loss).
Fortunately for me, I've not had any issues since I started doing a reboot after loading new books.
