Welcome! » Log In » Create A New Profile

rdiff-backup crashing

Posted by Anonymous 
rdiff-backup crashing
April 10, 2004 04:10AM
Gents,

I am having a problem.

History:
last week on the master file server a disk crashed. Its been returned to
the manufacturer under warrenty. Alas, it crashed during the backup.
Apparently the backup structure is inconsistent. I restored the data
from the backup onto a different disk and have had no complaint of the
users. BUT

later backups never completed. They started well, than slowed down to a
crawl. I've modified my backup server to let it complete, and after more
than 2 days such a backup was still incomplete. And the linux OOM killer
killed the running backup instance...
Normal backup time is less than 2 hours.

Version that showed this behaviour was 0.10.2
In an attempt to solve this i upgraded to 0.12.6 (and upgraded librsync
to 0.9.6). To do this consistently (and because i had other reasons to
do this as well) i've also upgraded from slackware 7 based distro to
slackware-current as of 2 weeks ago (which includes an upgrade from
python 2.2 to python 2.3.3).

disk mappings are unchanged.

I now get the following error from rdiff-backup:

root < at > backup:~# rdiff-backup --force -v 6 /src/garion-public/
/backup/garion-public/
Touching mirror marker
/backup/garion-public/rdiff-backup-data/current_mirror.2004-04-10T12:11:10+02:00.data
Warning: Metadata file not found.
Metadata will be read from filesystem.
Processing changed file .
Incrementing mirror file /backup/garion-public
Traceback (most recent call last):
File "/usr/local/bin/rdiff-backup", line 23, in ?
rdiff_backup.Main.Main(sys.argv[1:])
File "/usr/lib/python2.3/site-packages/rdiff_backup/Main.py", line
250, in Main
take_action(rps)
File "/usr/lib/python2.3/site-packages/rdiff_backup/Main.py", line
222, in take_action
elif action == "backup": Backup(rps[0], rps[1])
File "/usr/lib/python2.3/site-packages/rdiff_backup/Main.py", line
264, in Backup
backup.Mirror_and_increment(rpin, rpout, incdir)
File "/usr/lib/python2.3/site-packages/rdiff_backup/backup.py", line
47, in Mirror_and_increment
DestS.patch_and_increment(dest_rpath, source_diffiter, inc_rpath)
File "/usr/lib/python2.3/site-packages/rdiff_backup/backup.py", line
220, in patch_and_increment
ITR(diff.index, diff)
File "/usr/lib/python2.3/site-packages/rdiff_backup/rorpiter.py", line
266, in __call__
else: self.root_branch.start_process(*args)
File "/usr/lib/python2.3/site-packages/rdiff_backup/backup.py", line
610, in start_process
self.get_incrp(index))
File "/usr/lib/python2.3/site-packages/rdiff_backup/backup.py", line
575, in inc_with_checking
try: inc = increment.Increment(new, old, inc_rp)
File "/usr/lib/python2.3/site-packages/rdiff_backup/increment.py",
line 41, in Increment
elif mirror.isdir(): incrp = makedir(mirror, incpref)
File "/usr/lib/python2.3/site-packages/rdiff_backup/increment.py",
line 94, in makedir
dirsign = get_inc(incpref, "dir")
File "/usr/lib/python2.3/site-packages/rdiff_backup/increment.py",
line 114, in get_inc
assert not incrp.lstat()
AssertionError
Exception exceptions.TypeError: "'NoneType' object is not callable" in
<bound method GzipFile.__del__ of <gzip open file
'/backup/garion-public/rdiff-backup-data/file_statistics.2004-04-10T12:11:10+02:00.data.gz',
mode 'wb' at 0x40403820 0x4066d7cc>> ignored
Exception exceptions.TypeError: "'NoneType' object is not callable" in
<bound method GzipFile.__del__ of <gzip open file
'/backup/garion-public/rdiff-backup-data/error_log.2004-04-10T12:11:10+02:00.data.gz',
mode 'wb' at 0x40403da0 0x4067204c>> ignored
Exception exceptions.TypeError: "'NoneType' object is not callable" in
<bound method GzipFile.__del__ of <gzip open file
'/backup/garion-public/rdiff-backup-data/mirror_metadata.2004-04-10T12:11:10+02:00.snapshot.gz',
mode 'wb' at 0x40403d60 0x4068228c>> ignored

This happens only on the backup set which was being backed-up during the
disk crash. All other backup sets are unharmed and get a backup without
any problem.
rdiff-backup crashing
April 10, 2004 04:11PM
Rudy L. Zijlstra wrote:

[quote]This happens only on the backup set which was being backed-up during the
disk crash. All other backup sets are unharmed and get a backup without
any problem.
[/quote]
if you are willing to forgo your increments, you could rm -rf
rdiff-backup-data dir and see if that fixes it.

dave
rdiff-backup crashing
April 10, 2004 04:20PM
David Kempe wrote:

[quote]Rudy L. Zijlstra wrote:

[quote]This happens only on the backup set which was being backed-up during
the disk crash. All other backup sets are unharmed and get a backup
without any problem.
[/quote]

if you are willing to forgo your increments, you could rm -rf
rdiff-backup-data dir and see if that fixes it.

dave
[/quote]
Sigh,

I am doing something very close. I've copied the backup mirror - I
really like those increments - to a spare disk and will first try your
suggestion, if that fails, i will completly start anew. And not use that
spare disk for the coming half year (thats how long i keep the increments).

Rudy
Sorry, only registered users may post in this forum.

Click here to login