I'm not sure if this is relevant or helps, but I was googling for "zlib.error: Error -3 while decompressing: invalid block type" and other than this very thread, all of the other results were to do with mercurial or python stream decompression.
I meant to send the below reply to the list also. I really want to get to the bottom of this. ---------- Forwarded message ---------- From: Billy Crook <[email protected]> Date: Wed, Jun 10, 2009 at 11:29 Subject: Re: [rdiff-backup-users] "Broken" backup destination. Bug, or Disk error? To: Peter HOWELL <[email protected]> On Wed, Jun 10, 2009 at 03:27, Peter HOWELL<[email protected]> wrote: > Hi > > A quick look at you debug has an 'join acl' in it.... > > I am no expert or have fully read all your debug but.... > > putting --no-acls in the command line fixed all my problems and they all > work perfectly now. > > it might be worth a try until someone who really knows gives a more > analytical result ;-) > > Cheers > > Peter Howell hmm.... Well, both ext3 and ext4 (the source and destination filesystems) should support acls, but I'm not using them (AFAIK), so I tried the --no-acls argument, but it still turbofailed. What was the nature of the problems you solved by adding --no-acls? This time I posted the last bit of the strace'd rdiff error to http://bcrook.com/rdifflog20090610073051.tail _______________________________________________ rdiff-backup-users mailing list at [email protected] http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
