duplicity-talk
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Duplicity-talk] IOError: [Errno 28] No space left on device


From: Kenneth Loafman
Subject: Re: [Duplicity-talk] IOError: [Errno 28] No space left on device
Date: Sat, 28 Feb 2009 09:55:06 -0600
User-agent: Thunderbird 2.0.0.19 (X11/20090105)

I'm not sure what's going on either.  The growth sequence does not show
anything abnormal going on, and certainly nothing going on in /tmp which
is what we suspected.  The last file you've tried to restore is:
  controller/DATA FOLDER/db/out.log.old
and unless that is expanding to something huge, I don't see where its going.

I would suggest excluding that file with
  --exclude="controller/DATA FOLDER/db/out.log.old"
and trying the restore again.  Its possible something got corrupted and
is causing the decryption/decompression to go haywire.

At this point, I'm just trying to isolate the problem.

...Ken

enderst wrote:
> I've also attached a log i generated showing filesystem growth with df
> -h and du -sch /*
> doesn't make sense and i've been going nuts with this.
> 
> script used to get the growth log. something thrown together to get that
> output nothing more
> #!/bin/bash
> pid=1
> while [ $pid -gt 0 ]
> do
>         echo "**********************************"
>         date
>         echo "=================================="
>         df -h
>         echo "----------------------------------"
>         du -sch /*
>         echo
>         sleep 300
>         pid=$(ps ax|grep recovery.sh|grep -v grep|awk {'print $1'})
> done
> 
> duplicity command:
> duplicity -v9 --tempdir /mnt/ext/tmp --encrypt-key "xxxxxxxx"
> file:///mnt/ext/backup /mnt/ext/recovery > duplicity.log
> 
> enderst
> 
> 
> 
> On Fri, Feb 27, 2009 at 2:19 PM, Kenneth Loafman <address@hidden
> <mailto:address@hidden>> wrote:
> 
>     The --tempdir option should be working without the exports, assuming
>     /mnt/ext/tmp exists and is writable.  I've seen some distro's silently
>     ignore attempts to change /tmp to a non-existant directory and default
>     to /tmp anyway.
> 
>     If you put a watch of "du -sh /tmp" you could tell if /tmp is growing.
>     It should not grow by much.  If it does, then send the first 200 lines
>     of the log and the last 200 lines of the log plus the command line.
> 
>     FYI: You might try "du -shc /*".  --max-depth may be confusing the issue
>     since duplicity would create $TMP/duplicity-foo subdirs.  This would
>     show /tmp as well.
> 
>     ...Ken
> 
>     enderst wrote:
>     > Trying to restore files and I keep getting the error in the subject.
>     >
>     > tried - duplicity -v9 --tempdir /mnt/ext/tmp --encrypt-key "xxxxxxxx"
>     > file:///mnt/ext/backup /mnt/ext/recovery
>     >
>     > After searching for diskspace errors thought maybe I needed
>     something like:
>     > #!/bin/bash
>     > export TMP=/mnt/ext/tmp
>     > export TMPDIR=/mnt/ext/tmp
>     > export TEMP=/mnt/ext/tmp
>     > duplicity -v9 --tempdir /mnt/ext/tmp --encrypt-key "xxxxxxxx"
>     > file:///mnt/ext/backup /mnt/ext/recovery
>     >
>     > ----------------------------------------
>     >
>     > /mnt/ext is a 500G drive. while running the restore everything seems
>     > fine but, I have 'watch df -h' running in a terminal and can see
>     > diskspace being consumed but can't tell with 'du -ch --max-depth=1 /'
>     > where it's going.
>     >
>     > the distro is ArchLinux and was installed on a 10G drive just to
>     recover
>     > this backup thinking that setting the tempdir would eliminate
>     space issues.
>     > do i need to set the /tmp mountpoint to /mnt/ext/tmp ?
>     >
>     > python 2.6.1
>     > duplicity 0.5.09
>     > librsync 0.9.7
>     >
>     > AMD Athlon(tm) X2 Dual Core Processor BE-2400
>     > 2G Ram
>     >
>     > 48G backup includes incrementals
>     > 593 duplicity files volsize at 100mb
>     >
>     > Collection Status
>     > -----------------
>     > Connecting with backend: LocalBackend
>     > Archive dir: None
>     >
>     > Found 0 backup chains without signatures.
>     >
>     > Found a complete backup chain with matching signature chain:
>     > -------------------------
>     > Chain start time: Tue Jan 13 15:57:47 2009
>     > Chain end time: Tue Feb 24 19:30:02 2009
>     > Number of contained backup sets: 43
>     > Total number of contained volumes: 507
>     >  Type of backup set:                            Time:      Num
>     volumes:
>     >                 Full         Tue Jan 13 15:57:47 2009            
>       319
>     >          Incremental         Wed Jan 14 19:30:02 2009            
>        11
>     >          Incremental         Thu Jan 15 19:30:02 2009            
>         5
>     >          Incremental         Fri Jan 16 19:30:01 2009            
>         7
>     >          Incremental         Sat Jan 17 19:30:02 2009            
>        12
>     >          Incremental         Sun Jan 18 19:30:02 2009            
>         6
>     >          Incremental         Mon Jan 19 19:30:02 2009            
>         5
>     >          Incremental         Tue Jan 20 19:30:02 2009            
>        12
>     >          Incremental         Wed Jan 21 19:30:02 2009            
>         7
>     >          Incremental         Thu Jan 22 19:30:02 2009            
>         3
>     >          Incremental         Fri Jan 23 19:30:01 2009            
>         1
>     >          Incremental         Sat Jan 24 19:30:01 2009            
>         1
>     >          Incremental         Sun Jan 25 19:30:02 2009            
>         1
>     >          Incremental         Mon Jan 26 19:30:02 2009            
>         1
>     >          Incremental         Tue Jan 27 19:30:01 2009            
>         1
>     >          Incremental         Wed Jan 28 19:30:02 2009            
>         1
>     >          Incremental         Thu Jan 29 19:30:01 2009            
>         1
>     >          Incremental         Fri Jan 30 19:30:01 2009            
>         1
>     >          Incremental         Sat Jan 31 19:30:02 2009            
>         1
>     >          Incremental         Sun Feb  1 19:30:02 2009            
>         1
>     >          Incremental         Mon Feb  2 19:30:01 2009            
>         1
>     >          Incremental         Tue Feb  3 19:30:02 2009            
>         1
>     >          Incremental         Wed Feb  4 19:30:02 2009            
>         1
>     >          Incremental         Thu Feb  5 19:30:02 2009            
>         1
>     >          Incremental         Fri Feb  6 19:30:01 2009            
>         1
>     >          Incremental         Sat Feb  7 19:30:02 2009            
>         1
>     >          Incremental         Sun Feb  8 19:30:02 2009            
>         1
>     >          Incremental         Mon Feb  9 19:30:01 2009            
>         1
>     >          Incremental         Tue Feb 10 19:30:01 2009            
>         1
>     >          Incremental         Wed Feb 11 19:30:02 2009            
>         1
>     >          Incremental         Thu Feb 12 19:30:01 2009            
>         1
>     >          Incremental         Fri Feb 13 19:30:02 2009            
>         1
>     >          Incremental         Sat Feb 14 19:30:02 2009            
>         1
>     >          Incremental         Sun Feb 15 19:30:02 2009            
>         1
>     >          Incremental         Mon Feb 16 19:30:02 2009            
>        10
>     >          Incremental         Tue Feb 17 19:30:02 2009            
>        13
>     >          Incremental         Wed Feb 18 19:30:02 2009            
>         7
>     >          Incremental         Thu Feb 19 19:30:01 2009            
>        16
>     >          Incremental         Fri Feb 20 19:30:01 2009            
>         6
>     >          Incremental         Sat Feb 21 19:30:02 2009            
>         8
>     >          Incremental         Sun Feb 22 19:30:01 2009            
>         5
>     >          Incremental         Mon Feb 23 19:30:02 2009            
>        16
>     >          Incremental         Tue Feb 24 19:30:02 2009            
>        15
>     > -------------------------
>     > No orphaned or incomplete backup sets found.
>     >
>     >
>     > Traceback (most recent call last):
>     >   File "/usr/bin/duplicity", line 582, in <module>
>     >     with_tempdir(main)
>     >   File "/usr/bin/duplicity", line 576, in with_tempdir
>     >     fn()
>     >   File "/usr/bin/duplicity", line 539, in main
>     >     restore(col_stats)
>     >   File "/usr/bin/duplicity", line 299, in restore
>     >     restore_get_patched_rop_iter(col_stats)):
>     >   File "/usr/lib/python2.6/site-packages/duplicity/patchdir.py", line
>     > 463, in Write_ROPaths
>     >     for ropath in rop_iter:
>     >   File "/usr/lib/python2.6/site-packages/duplicity/patchdir.py", line
>     > 438, in integrate_patch_iters
>     >     final_ropath = patch_seq2ropath(normalize_ps(patch_seq))
>     >   File "/usr/lib/python2.6/site-packages/duplicity/patchdir.py", line
>     > 418, in patch_seq2ropath
>     >     misc.copyfileobj(current_file, tempfp)
>     >   File "/usr/lib/python2.6/site-packages/duplicity/misc.py", line 156,
>     > in copyfileobj
>     >     outfp.write(buf)
>     > IOError: [Errno 28] No space left on device
>     >
>     >
>     >
>     ------------------------------------------------------------------------
>     >
>     > _______________________________________________
>     > Duplicity-talk mailing list
>     > address@hidden <mailto:address@hidden>
>     > http://lists.nongnu.org/mailman/listinfo/duplicity-talk
> 
> 
> 
>     _______________________________________________
>     Duplicity-talk mailing list
>     address@hidden <mailto:address@hidden>
>     http://lists.nongnu.org/mailman/listinfo/duplicity-talk
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Duplicity-talk mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/duplicity-talk


Attachment: signature.asc
Description: OpenPGP digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]