I'm restoring a big file (~80GB, a virtual machine disk image).
Although I start the restore operation with >145GB disk space, as reported by
df , the restore aborts with a message that my disk has only 900MB available. After the stoppage, I have a 64GB (partial, unusable) .vdi file in the target directory, while
df reports that I have 81GB available.
(The latter number really looks like the same number as the size of the file being restored... is it a coincidence? If it checks that it has enough disk space to save the whole file until the end, in practice it would require twice the room!)
How come deja-dup (duplicity) aborts the operation if there is still so much disk space? What should I do to get my file restored?
PS. I saw that at the beginning (so called preparation) the available capacity starts to decrease (as reported by
df) even before seeing any file being written in the target directory. Where does deja-dup (duplicity) write preliminary data, and what does it write? I see that something goes into ~/.cache/deja-dup, but it occupies "only" 2.1GB...