Quote:
Originally Posted by theducks
Dropbox or any other connection that can write (or block a calibre write) to the Library folder.
Write behind (delayed) caching is another culprit.
Antivirus scans can block a change.  Exclude the Library folder from a 'realtime' scan.
IMHO another problem with using 'the cloud' : Everything in my library has been scanned BEFORE it arrived. With the cloud, it seems possible to inject a contaminated copy if real time scanning has been excluded for structure integrity purposes . (like preventing your problem?) |
I do have security software that might have decided to scan at exactly that moment. I'll tell it to not worry about my ebooks.
I don't sync my library anywhere, so it's not an issue with that.
If Calibre can't handle the standard Windows caching methods, than that is a problem with Calibre. I don't think that's the case, though. An OS feature that's been standard for years shouldn't be able to cause book loss except with egregiously inflexible coding. There would be many, many more reports of this issue if that was the case, so I don't think it's related to caching.
My workaround will at least keep books from being lost, so that's something. It's still incredibly frustrating. Hopefully I'll be able to reproduce it.
Could it be related to multiple libraries? I do have several different Calibre libraries and move books between them fairly often using Calibre's standard move-book functionality. If swapping books around isn't something that Calibre can handle well that's at least an explanation that can be worked around.