Quote:
Originally Posted by Calenorn
I am WAY out of my depth here, but is it possible that sometimes a process is still running when the device is ejected? If so, would it be logical to suspect that a newly occurring error it is related to the newly added (note-taking) firmware?
|
This is probably what is happening. But, it will be a process left running when the device is connected to the PC. That will probably keep the filesystem open, and Windows will detect this as dirty. And if the database is open, then it could result in a corrupt database.
A problem like this was actually fixed in firmware 4.30. There was an apparently long-standing issue with the comic reader on the device. This did not close properly and resulted in issues if you connected to the PC and something (calibre, the Kobo desktop, etc) the database. If you didn't read comics, you never saw it. This was fixed as soon as it was reported.
Something similar seems to be happening here. Especially as restarting the device seems to prevent the issues. That will close all processes and that should result in a clean file system. It seems to be something in the import process, but, proving that is difficult.
Quote:
The reason I left NOOK for Kobo was that the Glowlight 3 seemed to recopy all sideloaded books anytime I added even one new book. This was a SLOW process, and had the annoying side effect of removing the sideloaded books from any user created shelves on the device. My Windows 8 machine would display "safe to remove" message when that clearly was NOT true for the Glowlight3.
The point is, a note-taking device would have to update the notes on EVERY book, wouldn't it? The larger the library, the longer this would take. Might be interesting to see if the problems occur more often on bulkier libraries.
|
The annotations on Kobo devices are handled in two ways. For annotations in PDFs made using the stylus, they are written to the file. And they are written when the books is closed. Other annotations are stored in the database. As far as I can tell, these are written to the database as they are made.
Quote:
I found this article interesting:
https://www.hellotech.com/blog/reall...ect-usb-drives
Particularly this bit:
"However, even if the USB is not in active use, there is still a danger of corrupting the files. Most operating systems use a caching process. This means that the data is not written immediately onto the USB drive. Some of this information could still be stored on your computer’s RAM.
When you perform a copy command, the computer (depending on the operating system) might perform a series of requests. This can lengthen the process of transferring data from the computer to the USB. This is especially true when you are handling a large amount of data or files."
Suggests that the problem might depend on the operating system, no?
|
That is correct. If you unplug the device at the wrong time it can cause issues. But, the device is the one in control when plugging in to the PC. Seeing what is left open at that time is hard. It has to be done from the device, and that is a pain.