View Single Post
Old 05-08-2023, 03:02 PM   #6
bonzi
Enthusiast
bonzi once ate a cherry pie in a record 7 seconds.bonzi once ate a cherry pie in a record 7 seconds.bonzi once ate a cherry pie in a record 7 seconds.bonzi once ate a cherry pie in a record 7 seconds.bonzi once ate a cherry pie in a record 7 seconds.bonzi once ate a cherry pie in a record 7 seconds.bonzi once ate a cherry pie in a record 7 seconds.bonzi once ate a cherry pie in a record 7 seconds.bonzi once ate a cherry pie in a record 7 seconds.bonzi once ate a cherry pie in a record 7 seconds.bonzi once ate a cherry pie in a record 7 seconds.
 
bonzi's Avatar
 
Posts: 46
Karma: 1530
Join Date: Nov 2011
Location: Zagreb, Croatia
Device: K2i, K3/KK WiFi, Basic (old), 2xFire, 2xPW (old), Voyage, Scribe
Quote:
Originally Posted by kovidgoyal View Post
yes that's most likely a disk full error. Use a larger disk to export too or alternately disable full text indexing and delete the full-text-search.db file in the calibre library folder before exporting. You will then have to re-enable and re-index the library.
I checked, and there was plenty of space on the target disk. However, does this operation use some space on the system disk, too, perhaps in AppData? At the start, the program shows that the lib has some 50GB; the export target drive has about 350GB free. However, during the very short lived operation something ate the last 13GB of space on my system disk.

Any ideas?

Thanks!

Update: Yes, c:/users/%myself%/AppData/Local/Temp/calibre_1q_z10g2/dor8jxw9-export.db is the culprit. Is there a way to tell Calibre to use the temp space somewhere else?

Update: Yes, there is; CALIBRE_TEMP_DIR env. var.

Note to self: RTFM!

Thanks!

Last edited by bonzi; 05-09-2023 at 03:15 AM.
bonzi is offline   Reply With Quote