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

[edgar . soldin]

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