Quote:
Originally Posted by JvdW
I'll backup my books from IM and SD card and format both and re-upload the books to see if the problem goes away. Looks like one OS uses ctime and the other mtime. Can imagine that since you can't have a ctime after mtime (c=create, m=modify)
|
I was wrong when I said ctime. Calibre uses mtime.
Your point could be significant. FAT and FAT32 provide both mtime and ctime. The two will be the same when a book is first sent to the device. However, when you resend a book with calibre, it does an open w/truncate, which should change the mtime but not the ctime. If (some version of) the sony SW uses ctime, updating a book will get calibre and sony permanently out of sync.
I will try some experiments on my 300, but what I see may not be the same behavior as other devices.
Perhaps the best thing to do would be to delete before add, which would result in the two timestamps always being the same. There would be no visible performance penalty (milliseconds), because writing the file takes the vast majority of time and both methods must do that.