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

[4qgo8vv02]

Hi everyone,

I've been using duplicity for months and I'm now in the make-or-break
moment with a lump in my throat where I'm counting on it to restore my
backup.

I'm trying to do a full restore into a Mac OS Leopard "sparse bundle".
 A sparse bundle is basically an encrypted disk image that Mac OS uses
to encrypt the user's home directory.  My hard disk size is 150GB,
which is more than enough room for my files, and the sparse bundle
created by Mac OS has a maximum capacity of 300GB.  My restore is
failing because it's somehow running out of disk space:

Traceback (most recent call last):
  File "/opt/local/bin/duplicity", line 424, in <module>
    if __name__ == "__main__": with_tempdir(main)
  File "/opt/local/bin/duplicity", line 420, in with_tempdir
    fn()
  File "/opt/local/bin/duplicity", line 400, in main
    if action == "restore": restore(col_stats)
  File "/opt/local/bin/duplicity", line 200, in restore
    restore_get_patched_rop_iter(col_stats)):
  File "/opt/local/lib/python2.5/site-packages/duplicity/patchdir.py",
line 456, in Write_ROPaths
    for ropath in rop_iter:
  File "/opt/local/lib/python2.5/site-packages/duplicity/patchdir.py",
line 431, in integrate_patch_iters
    final_ropath = patch_seq2ropath(normalize_ps(patch_seq))
  File "/opt/local/lib/python2.5/site-packages/duplicity/patchdir.py",
line 411, in patch_seq2ropath
    misc.copyfileobj(current_file, tempfp)
  File "/opt/local/lib/python2.5/site-packages/duplicity/misc.py",
line 153, in copyfileobj
    outfp.write(buf)
IOError: [Errno 28] No space left on device

Just before duplicity stopped, I saw that disk space was running low
on the sparse bundle:

bash-3.2# df -h
Filesystem                                Size   Used  Avail Capacity
Mounted on
/dev/disk2s2                             297Gi  296Gi  1.4Gi   100%
/Volumes/David

Immediately after duplicity crashed, I suddenly had 115 more GB free!

bash-3.2# df -h
Filesystem                                Size   Used  Avail Capacity
Mounted on
/dev/disk2s2                             297Gi  181Gi  116Gi    61%
/Volumes/David

It's as though the duplicity restore process was somehow using 115GB
of temporary files to do its work.  Before it crashed, I tried to find
out where the space was being used, but I couldn't.  There wasn't much
in /tmp.

I don't know if this is a duplicity problem or a sparse bundle
problem.  I'm desperate to get up and running again, so I'm going to
forgo encryption for now by turning off the sparse bundle feature,
start the 12 hour restore process again, and hope it works this time.
Does anyone have any insight into why this is failing?  Is it possible
that duplicity is creating 100GB of temporary files during the
restore?

Thanks,
David