View Single Post
Old 03-05-2014, 04:33 AM   #29
chaley
Grand Sorcerer
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 12,476
Karma: 8025702
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
@z.nina: what filesystem is used on the second drive? I ask because on Windows, whenever the database is changed the database manager (sqlite3) creates a log file, writes recovery information to it, changes the db, then deleted the log file. It you are using an odd file system then that create/write/delete cycle could be the culprit. If you are using NTFS, it probably isn't the issue.

Another thing to check is whether write-behind caching is turned off on the second drive. Go to the device manager, right-click on the disc in question, choose Properties, and check in the "Policies" section. Turning off write-behind caching would be catastrophic for calibre performance.
chaley is offline   Reply With Quote