duplicity-talk
[Top][All Lists]
Advanced

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

Re: [Duplicity-talk] problems with the temp dir


From: edgar . soldin
Subject: Re: [Duplicity-talk] problems with the temp dir
Date: Tue, 12 Jun 2012 18:34:38 +0200
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1

well spotted, was about to suggest this next. anyway, you really should clean 
up your / partition it seems to be stuffed full. you could start by deleting 
the old archive folder '/root/.cache/duplicity'.

consider using /tmp as your TMP location as duplicity only needs it to be as 
big as your biggest file (on restoring) or two time your volume size (on 
backing up).

..ede/duply.net

On 12.06.2012 17:58, jbiskofski wrote:
> I got it working, I needed to set my archive-dir apart from the tempdir, I 
> did this and now its working. Thanks for the help.
> 
> - Jose
> 
> On Tue, Jun 12, 2012 at 10:50 AM, jbiskofski <address@hidden 
> <mailto:address@hidden>> wrote:
> 
>     Edgar thanks for the response
> 
>     Here is my mount and df -h output : 
> 
>     node05# mount
>     /dev/ad4s1a on / (ufs, local)
>     devfs on /dev (devfs, local, multilabel)
>     /dev/ad4s1e on /tmp (ufs, local, soft-updates)
>     /dev/ad4s1f on /usr (ufs, local, soft-updates)
>     /dev/ad4s1d on /var (ufs, local, soft-updates)
>     /dev/ad6s1d on /usr/local/postgres/data (ufs, local, soft-updates)
>     devfs on /var/named/dev (devfs, local, multilabel)
>     172.24.8.201:/tank/ss6868 on /mnt/nas (nfs)
> 
>     node05# df -h
>     Filesystem                   Size    Used   Avail Capacity  Mounted on
>     /dev/ad4s1a                  989M    984M    -74M   108%    /
>     devfs                        1.0K    1.0K      0B   100%    /dev
>     /dev/ad4s1e                  989M     50K    910M     0%    /tmp
>     /dev/ad4s1f                  426G     43G    349G    11%    /usr
>     /dev/ad4s1d                   19G     66M     18G     0%    /var
>     /dev/ad6s1d                   58G    4.5G     49G     8%    
> /usr/local/postgres/data
>     devfs                        1.0K    1.0K      0B   100%    /var/named/dev
>     172.24.8.201:/tank/ss6868     10G    633M    9.4G     6%    /mnt/nas
> 
>     ===
> 
>     here is the duplicity command im running : 
> 
>     /usr/local/bin/duplicity -v debug 
> --tempdir=/usr/local/algebraix/backup/_TEMP/duplicity-tmp \\
>     /usr/local/algebraix/backup/_TEMP/database.db \\
>     s3+http://XXXXXXX/customers/XXXXXXX/db/XXXXXXXX/
> 
> 
>     and here is the error in pastebin : 
> 
>     http://pastebin.com/dWB8UGxG
> 
>     Thanks!
> 
>     - Jose
> 
> 
> 
>     On Tue, Jun 12, 2012 at 10:36 AM, <address@hidden 
> <mailto:address@hidden>> wrote:
> 
>         On 12.06.2012 17:23, jbiskofski wrote:
>         > Hi everyone,
>         >
>         > Im running duplicity on a dedicated server with a pretty bad 
> partitioning scheme, I have 128MB in /
>         >
>         > I set the "--tempdir=/usr/local/backup/duplicity-tmp" option for 
> duplicity to avoid problems but Im still getting the following error :
>         >
>         > /: write failed, filesystem is full
>         > Traceback (most recent call last):
>         >   File "/usr/local/bin/duplicity", line 1391, in <module>
>         >     with_tempdir(main)
>         >   File "/usr/local/bin/duplicity", line 1384, in with_tempdir
>         >     fn()
>         >   File "/usr/local/bin/duplicity", line 1366, in main
>         >     incremental_backup(sig_chain)
>         >   File "/usr/local/bin/duplicity", line 572, in incremental_backup
>         >     globals.backend)
>         >   File "/usr/local/bin/duplicity", line 378, in write_multivol
>         >     globals.gpg_profile, globals.volsize)
>         >   File "/usr/local/lib/python2.6/site-packages/duplicity/gpg.py", 
> line 320, in GPGWriteFile
>         >     data = block_iter.next(min(block_size, bytes_to_go)).data
>         >   File 
> "/usr/local/lib/python2.6/site-packages/duplicity/diffdir.py", line 504, in 
> next
>         >     result = self.process_continued(size)
>         >   File 
> "/usr/local/lib/python2.6/site-packages/duplicity/diffdir.py", line 676, in 
> process_continued
>         >     data, last_block = self.get_data_block(self.process_fp, size - 
> 512)
>         >   File 
> "/usr/local/lib/python2.6/site-packages/duplicity/diffdir.py", line 660, in 
> get_data_block
>         >     buf = fp.read(read_size)
>         >   File 
> "/usr/local/lib/python2.6/site-packages/duplicity/librsync.py", line 80, in 
> read
>         >     self._add_to_outbuf_once()
>         >   File 
> "/usr/local/lib/python2.6/site-packages/duplicity/librsync.py", line 90, in 
> _add_to_outbuf_once
>         >     self._add_to_inbuf()
>         >   File 
> "/usr/local/lib/python2.6/site-packages/duplicity/librsync.py", line 105, in 
> _add_to_inbuf
>         >     assert not self.infile.close()
>         >   File 
> "/usr/local/lib/python2.6/site-packages/duplicity/diffdir.py", line 431, in 
> close
>         >     self.callback(self.sig_gen.getsig(), *self.extra_args)
>         >   File 
> "/usr/local/lib/python2.6/site-packages/duplicity/diffdir.py", line 123, in 
> callback
>         >     sigTarFile.addfile(ti, cStringIO.StringIO(sig_string))
>         >   File 
> "/usr/local/lib/python2.6/site-packages/duplicity/tarfile.py", line 2025, in 
> addfile
>         >     copyfileobj(fileobj, self.fileobj, tarinfo.size)
>         >   File 
> "/usr/local/lib/python2.6/site-packages/duplicity/tarfile.py", line 275, in 
> copyfileobj
>         >     dst.write(buf)
>         >   File 
> "/usr/local/lib/python2.6/site-packages/duplicity/dup_temp.py", line 151, in 
> write
>         >     return self.fileobj.write(buf)
>         > IOError: [Errno 28] No space left on device
>         >
>         >
>         > =====
>         >
>         >
>         > any ideas? I was a big fan of rdiff-backup and now Im a big fan of 
> duplicity, thanks for the great software.
>         >
> 
> 
>         are you sure that /usr/local/backup/duplicity-tmp is really on a 
> different filessystem with more free space? please do a 'df -h' as well as a 
> 'mount' for us and post the output.
> 
>         also please rerun your duplicity command ffrom above with maximum 
> verbosity '-v debug', obfuscate private data in it's output, pastebin it and 
> send the link so we can have a look at what is happening.
> 
>         ..ede/duply.net <http://duply.net>
> 
> 
> 
>         _______________________________________________
>         Duplicity-talk mailing list
>         address@hidden <mailto:address@hidden>
>         https://lists.nongnu.org/mailman/listinfo/duplicity-talk
> 
> 
> 
> 
> 
> _______________________________________________
> Duplicity-talk mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/duplicity-talk



reply via email to

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