backup via localbackend fails sometimes

[Christian Ruppert]

backup via localbackend fails sometimes. I'm not sure if that is related but I always do a "cleanup" first. (cleanup/remove-older-than/remove-all-but-n-full/remove-all-inc-of-but-n-full)

Traceback (most recent call last):
  File "/usr/bin/duplicity", line 1245, in <module>
    with_tempdir(main)
  File "/usr/bin/duplicity", line 1238, in with_tempdir
    fn()
  File "/usr/bin/duplicity", line 1220, in main
    incremental_backup(sig_chain)
  File "/usr/bin/duplicity", line 488, in incremental_backup
    globals.backend)
  File "/usr/bin/duplicity", line 316, in write_multivol
    (tdp, dest_filename)))
  File "/usr/lib64/python2.6/site-packages/duplicity/asyncscheduler.py", line 145, in schedule_task
    return self.__run_synchronously(fn, params)
  File "/usr/lib64/python2.6/site-packages/duplicity/asyncscheduler.py", line 171, in __run_synchronously
    ret = fn(*params)
  File "/usr/bin/duplicity", line 315, in <lambda>
    async_waiters.append(io_scheduler.schedule_task(lambda tdp, dest_filename: put(tdp, dest_filename),
  File "/usr/bin/duplicity", line 241, in put
    backend.put(tdp, dest_filename)
  File "/usr/lib64/python2.6/site-packages/duplicity/backends/localbackend.py", line 57, in put
    target_path.writefileobj(source_path.open("rb"))
  File "/usr/lib64/python2.6/site-packages/duplicity/path.py", line 589, in writefileobj
    fout = self.open("wb")
  File "/usr/lib64/python2.6/site-packages/duplicity/path.py", line 531, in open
    result = open(self.name, mode)
IOError: [Errno 2] No such file or directory: '/mnt/backup/foo/duplicity-inc.20101214T174307Z.to.20101216T020302Z.vol1.difftar.gpg'

[Christian Ruppert (idl0r)]

Oh, I'm using 0.6.11 :)

[Kenneth Loafman (kenneth-loafman)]

From the path it appears you are using local backend to a mounted filesystem. If so, how is that FS mounted?

Just to note, duplicity does not retry on errors in the local backend. This is not a problem when using the local backend for local files, but can lead to problems when the files are remote.

[Christian Ruppert (idl0r)]

> From the path it appears you are using local backend to a mounted filesystem. If so, how is that FS mounted?

Currently via curlftpfs/fuse. It worked fine with previous versions.
The same issue appears on a second system where it's simply a ext4 partition.