Follow-up Comment #3, bug #25138 (project duplicity):
I re-ran duplicity on my Documents folder again. This time, with a completely
new/clean target (remote) directory, and new/clean archive and temp
directories. I got a different error this time:
Deleting
/cygdrive/e/DUPLICITY2/tmp/duplicity-AfQqG--tempdir/mktemp-xoK3lj-438
Forgetting temporary file
/cygdrive/e/DUPLICITY2/tmp/duplicity-AfQqG--tempdir/mktemp-xoK3lj-438
AsyncScheduler: task completed successfully
Using temporary directory
/cygdrive/e/DUPLICITY2/archive/duplicity-g1RBzD-tempdir
Registering (mktemp) temporary file
/cygdrive/e/DUPLICITY2/archive/duplicity-g1RBzD-tempdir/mktemp-duHxvl-1
Removing still remembered temporary file
/cygdrive/e/DUPLICITY2/tmp/duplicity-AfQqG--tempdir/mktemp-g9oSRI-1
Cleanup of temporary directory
/cygdrive/e/DUPLICITY2/tmp/duplicity-AfQqG--tempdir failed - this is probably
a bug.
Traceback (most recent call last):
File "/usr/bin/duplicity", line 553, in <module>
with_tempdir(main)
File "/usr/bin/duplicity", line 547, in with_tempdir
fn()
File "/usr/bin/duplicity", line 537, in main
full_backup(col_stats)
File "/usr/bin/duplicity", line 227, in full_backup
bytes_written = write_multivol("full", tarblock_iter, globals.backend)
File "/usr/bin/duplicity", line 165, in write_multivol
bytes_written += write_manifest(mf, backup_type, backend)
File "/usr/bin/duplicity", line 181, in write_manifest
fin.close()
File "/usr/lib/python2.5/site-packages/duplicity/dup_temp.py", line 121, in
close
hook()
File "/usr/lib/python2.5/site-packages/duplicity/dup_temp.py", line 62, in
rename_and_forget
tdp.rename(dirpath.append(filename))
File "/usr/lib/python2.5/site-packages/duplicity/path.py", line 514, in
rename
os.rename(self.name, new_path.name)
OSError: [Errno 2] No such file or directory
Removing still remembered temporary file
/cygdrive/e/DUPLICITY2/archive/duplicity-g1RBzD-tempdir/mktemp-duHxvl-1
Removing still remembered temporary file
/cygdrive/e/DUPLICITY2/archive/duplicity-hz6Z20-tempdir/mktemp-t5Awjw-1
I look on my E: drive for duplicity-AfQqG--tempdir/mktemp-g9oSRI-1 and indeed
it does not exist.
I'm re-running after this failure to see if subsequent failures give the bad
file descriptor error. Maybe it's a combination of a bad state on the remote
end. I'll keep you posted.
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?25138>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/
_______________________________________________
Duplicity-tracker mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/duplicity-tracker
