[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Duplicity-tracker] [bug #23715] Retry after upload error succeeds, but
From: |
anonymous |
Subject: |
[Duplicity-tracker] [bug #23715] Retry after upload error succeeds, but removed + before timezone offset, thus breaking restore |
Date: |
Thu, 26 Jun 2008 20:44:42 +0000 |
User-agent: |
Opera/9.23 (X11; Linux i686; U; en) |
URL:
<http://savannah.nongnu.org/bugs/?23715>
Summary: Retry after upload error succeeds, but removed +
before timezone offset, thus breaking restore
Project: duplicity
Submitted by: None
Submitted on: Donnerstag 26.06.2008 um 20:44 UTC
Category: None
Severity: 3 - Normal
Item Group: None
Status: None
Privacy: Public
Assigned to: None
Originator Email:
Open/Closed: Open
Discussion Lock: Any
_______________________________________________________
Details:
I just ran my initial full backup to an S3 bucket with duplicity 0.4.10 on
Ubuntu 8.04, 2.6.24-18-generic:
duplicity /home/carsten s3+http://calebackup
Completed fine (after ca. 45 hours), but three files listed "upload failed,
retrying". No problem so far since the retries went through fine.
However, when trying to restore the backup, it aborted with
Traceback (most recent call last):
File "/usr/bin/duplicity", line 463, in <module>
with_tempdir(main)
File "/usr/bin/duplicity", line 458, in with_tempdir
fn()
File "/usr/bin/duplicity", line 428, in main
restore(col_stats)
File "/usr/bin/duplicity", line 206, in restore
restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.5/site-packages/duplicity/patchdir.py", line 458, in
Write_ROPaths
ITR(ropath.index, ropath)
File "/usr/lib/python2.5/site-packages/duplicity/lazy.py", line 297, in
__call__
last_branch.fast_process, args)
File "/usr/lib/python2.5/site-packages/duplicity/robust.py", line 31, in
check_common_error
try: return function(*args)
File "/usr/lib/python2.5/site-packages/duplicity/patchdir.py", line 504, in
fast_process
if ropath.exists(): ropath.copy(self.base_path.new_index(index))
File "/usr/lib/python2.5/site-packages/duplicity/path.py", line 357, in
copy
if self.isreg(): other.writefileobj(self.open("rb"))
File "/usr/lib/python2.5/site-packages/duplicity/path.py", line 502, in
writefileobj
buf = fin.read(_copy_blocksize)
File "/usr/lib/python2.5/site-packages/duplicity/patchdir.py", line 171, in
read
if not self.addtobuffer(): break
File "/usr/lib/python2.5/site-packages/duplicity/patchdir.py", line 192, in
addtobuffer
try: self.tarinfo_list[0] = self.tar_iter.next()
File "/usr/lib/python2.5/site-packages/duplicity/patchdir.py", line 287, in
next
self.set_tarfile()
File "/usr/lib/python2.5/site-packages/duplicity/patchdir.py", line 278, in
set_tarfile
self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 230, in get_fileobj_iter
backup_set.volume_name_dict[vol_num],
KeyError: 507
Looking into my bucket, I noticed that three files have a space character in
front of the timezone offset instead of a +:
2008-06-25 15:50 5277021
s3://calebackup/duplicity-full.2008-06-24T18:54:24 02:00.vol507.difftar.gpg
2008-06-25 15:53 5287848
s3://calebackup/duplicity-full.2008-06-24T18:54:24 02:00.vol508.difftar.gpg
2008-06-25 15:56 5273937
s3://calebackup/duplicity-full.2008-06-24T18:54:24 02:00.vol509.difftar.gpg
2008-06-24 17:05 5236287
s3://calebackup/duplicity-full.2008-06-24T18:54:24+02:00.vol5.difftar.gpg
2008-06-24 19:06 5272421
s3://calebackup/duplicity-full.2008-06-24T18:54:24+02:00.vol50.difftar.gpg
2008-06-25 15:15 5271510
s3://calebackup/duplicity-full.2008-06-24T18:54:24+02:00.vol500.difftar.gpg
2008-06-25 15:19 5277901
s3://calebackup/duplicity-full.2008-06-24T18:54:24+02:00.vol501.difftar.gpg
2008-06-25 15:24 5284063
s3://calebackup/duplicity-full.2008-06-24T18:54:24+02:00.vol502.difftar.gpg
I suppose the successful retries ommitted the + in the file name using space
instead.
I have just "renamed" (got from s3, reput with new name) the files to contain
the plus and will post here if this worked. But even then, this is quite an
issue as for inexperienced users, a "successful" retry will silently break the
backup so that it cannot be restored any more.
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?23715>
_______________________________________________
Nachricht geschickt von/durch Savannah
http://savannah.nongnu.org/
- [Duplicity-tracker] [bug #23715] Retry after upload error succeeds, but removed + before timezone offset, thus breaking restore,
anonymous <=