duplicity - no space left on device?

So, I’m trying to restore some things from my previous Linux install (Ubuntu 12.10)… things like my Thunderbird mail directory and XChat config files, among other things. I backed up using Deja Dup on Ubuntu, so that was the first thing I tried on this end. No go, it wouldn’t even ask for the encryption password so it didn’t get very far. Didn’t really expect it to, but I was hoping.

Next I’ve been trying duplicity… at first I was just going to restore everything that had been in the old home directory into ~/temp/ and change permissions/ownership as needed and drop the files back as needed. Except I got an error like this:

Deleting /tmp/duplicity-lhEkTz-tempdir/mktemp-yxQM80-199
Processed volume 196 of 444
Deleting /tmp/duplicity-lhEkTz-tempdir/mktemp-R6i3kF-200
Processed volume 197 of 444
Traceback (most recent call last):
  File "/usr/bin/duplicity", line 1391, in <module>
    with_tempdir(main)
  File "/usr/bin/duplicity", line 1384, in with_tempdir
    fn()
  File "/usr/bin/duplicity", line 1318, in main
    restore(col_stats)
  File "/usr/bin/duplicity", line 623, in restore
    restore_get_patched_rop_iter(col_stats)):
  File "/usr/lib64/python2.7/site-packages/duplicity/patchdir.py", line 522, in Write_ROPaths
    for ropath in rop_iter:
  File "/usr/lib64/python2.7/site-packages/duplicity/patchdir.py", line 495, in integrate_patch_iters
    final_ropath = patch_seq2ropath( normalize_ps( patch_seq ) )
  File "/usr/lib64/python2.7/site-packages/duplicity/patchdir.py", line 475, in patch_seq2ropath
    misc.copyfileobj( current_file, tempfp )
  File "/usr/lib64/python2.7/site-packages/duplicity/misc.py", line 170, in copyfileobj
    outfp.write(buf)
IOError: [Errno 28] No space left on device

monte@hp-pc-lan:~/temp> 


So… since this install is a little cramped (~95GB for Linux, the other 500+ for Windows) and I set the installer to use LVM and a separate /home directory… and it allocated 20GB for / and 25GB for /home… and I’m not exactly sure WTF it did with the rest of that 95GB…

Anywho, even when I run ‘df’ at the command line, it doesn’t show any one file system at more than 27% full for /, /boot or /home. So how is duplicity running out of space so soon?

On 12/05/2012 06:16 AM, memilanuk wrote:
> So how is
> duplicity running out of space so soon?

i guess during the process of unpacking and whatever duplicity it
putting temporary stuff into /tmp or /var/tmp and filling it up…

you might not see the fullness after the fact, because when duplicity
dies maybe it releases those temporary files into the bit bucket…poof…

but, really it IS a guess as i have no idea how duplicity does what it
does… if i were gonna move from one distro to another i wouldn’t use
Deja Dup, Duplicity or anything else (that has its own private way of
doing stuff)…instead, on the old system i would use rsync to
populate an off machine medium, and then use rsync to copy that off
machine store to the new distro…

so, what i’m saying is: you may need to find a Deja Dup and Duplicity
expert to learn whats going on.


dd http://tinyurl.com/DD-Caveat

On 2012-12-05 10:19, dd wrote:
> On 12/05/2012 06:16 AM, memilanuk wrote:

> but, really it IS a guess as i have no idea how duplicity does what it
> does… if i were gonna move from one distro to another i wouldn’t use
> Deja Dup, Duplicity or anything else (that has its own private way of
> doing stuff)…instead, on the old system i would use rsync to
> populate an off machine medium, and then use rsync to copy that off
> machine store to the new distro…
>
> so, what i’m saying is: you may need to find a Deja Dup and Duplicity
> expert to learn whats going on.

True. I would have done the same, simply copy the files directly to
another disk. I have no experience with duplicity or deja dup… sorry.


Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

Gotcha… I’d hoped that since duplicity has been around for a while (10 years or so) and looks to be a python wrapper around some of the tools already mentioned (rsync, GNUpg, rdiff, etc.) that it might have some users/advocates here.

I’ll dig around elsewhere and see what I can find.