I believe i'm still experiencing the problems.
I have a set of backups from a machine which started with Ubuntu 12.04
and was upgraded a few weeks ago to 13.10. The backups were created via
deja-dup. I'm trying to restore on a Machine Running Linux Mint (
~Ubuntu 13.10) with duplicity 0.6.21-0ubuntu4.1.
Here's what i get when i try to restore my backup manually (duplicity, not
deja-dup):
python: ERROR: (rs_file_copy_cb) unexpected eof on fd122
python: ERROR: (rs_job_complete) patch job failed: unexpected end of input
Traceback (most recent call last):
File "/usr/bin/duplicity", line 1414, in <module>
with_tempdir(main)
File "/usr/bin/duplicity", line 1407, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1341, in main
restore(col_stats)
File "/usr/bin/duplicity", line 635, in restore
restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 526, in
Write_ROPaths
for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 499, in
integrate_patch_iters
final_ropath = patch_seq2ropath( normalize_ps( patch_seq ) )
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 479, in
patch_seq2ropath
misc.copyfileobj( current_file, tempfp )
File "/usr/lib/python2.7/dist-packages/duplicity/misc.py", line 166, in
copyfileobj
buf = infp.read(blocksize)
File "/usr/lib/python2.7/dist-packages/duplicity/librsync.py", line 80, in
read
self._add_to_outbuf_once()
File "/usr/lib/python2.7/dist-packages/duplicity/librsync.py", line 94, in
_add_to_outbuf_once
raise librsyncError(str(e))
librsyncError: librsync error 103 while in patch cycle
deja-dup detects that there's a problem and bails out. If i try to restore via
duplicity, i get this message and the application hangs.
A ps -ef ef shows that there's the duplicity process, which deja-dup started,
is still lingering around. My current process is idling.
Did i miss something?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1252484
Title:
Possible data loss when restarting in the middle of a deleted file
Status in Duplicity - Bandwidth Efficient Encrypted Backup:
Fix Committed
Status in “duplicity” package in Ubuntu:
Fix Released
Status in “duplicity” source package in Lucid:
Fix Committed
Status in “duplicity” source package in Precise:
Fix Committed
Status in “duplicity” source package in Quantal:
Fix Committed
Status in “duplicity” source package in Raring:
Fix Committed
Status in “duplicity” source package in Saucy:
Fix Released
Bug description:
This was recently fixed in duplicity trunk. But I'm filing a bug for
paperwork purposes and for Ubuntu SRUs.
[Impact]
When restarting a backup, duplicity may accidentally skip the first
65k chunk of one of the source files. This means that when it is
restored, it will be incomplete/corrupted, resulting in data loss.
[Test Case]
Download and install the 'test1.sh' file attached to this bug report, and run
it like 'sh test1.sh'. If it prints the following line, the bug is present:
Binary files /tmp/source/newfile and /tmp/restore/newfile differ
Or, follow these manual steps:
mkdir /tmp/source
dd if=/dev/urandom of=/tmp/source/bigfile bs=1024 count=5000
# This next command will intentionally fail after the second volume!
duplicity full /tmp/source file:///tmp/backup --vol 1 --fail 2 --no-encryption
mv /tmp/source/bigfile /tmp/source/newfile
duplicity full /tmp/source file:///tmp/backup --no-encryption
duplicity restore file:///tmp/backup /tmp/restore --no-encryption
# This next line will say the files differ if the bug is present
diff /tmp/source/newfile /tmp/restore/newfile
[Regression Potential]
It's a relatively small patch, only affecting the specific case of
restarting a backup when the file we were in the middle of is no
longer there. I'd say minor regression potential.
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1252484/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
