Quote:
Originally Posted by kovidgoyal
There's now ay a single add can cause the db to be continuously updated. Are you running some other calibre program accessing the db at the same time?
And no you cannot update custom field during an add, you should use calibredb set_metadata for that with the id printed by calibredb add (of course in your case since calibredb add is hanging you cannot do that).
|
I know there are no cmdline switches for now, I'm just asking if you maybe want to add such a switch so that I don't have to do that in two steps.
Ok, so for now, I ran the command on 16:11.
I can see calibre creating:
Koontz Dean subdir on 16:11
2003 (62602) on 16:11
2003 - Koontz Dean.epub on 16:11
from that time I can hear harddrive sounds and I can see metadata.db and metadata.db-journal being constantly updated.
No other calibre process is running, just calibredb.exe. Checked that in the task manager, there are also seen tens of thousands of read/writes. Right now, 7 minutes in running, I see 85MB of read data, 42MB of written data.
The db has 24MB, ebook 100kB.
After 10 minutes of running, I killed it. Also I have to note that this is 4-core XEON machine with nothing to do
and 16GB of memory, so we're not running under stressed condition here, or swapping.
HA! I ran procmon and it seems that it does something to .opf files in my library, tons of operations around them. Checked one of the changed .opfs, it seems that it somehow 'backups' the newly created custom metadata fields to them. So it means it's not unending, but extremely slow, also doing something 'automagically' without my consent. #metoo
