Re: [Duplicity-talk] restoring into sparsebundle fails with "No space left on device"

[Darik Horn]

> Is it possible that duplicity is creating 100GB of temporary
> files during the restore?

Yes, I've seen this behavior on Linux systems too.  It is not an 
incompatibility with sparse bundles.

Duplicity removes its temporary files but the file handles are not 
actually closed until the Python process exits, which means that you 
need twice the backup size available in /tmp to do the restore.

The /tmp directory may seem empty, but check the output of `lsof /tmp` 
while duplicity is running.