[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: dreaded "Decompression of svndiff data failed" question

From: Stefan Sperling <stsp_at_elego.de>
Date: Thu, 23 Jun 2011 22:34:54 +0200

On Thu, Jun 23, 2011 at 08:50:05AM +0200, martin wrote:
> Hi all,
>
> I've searched the list and could not find an answer to this.
>
> I've run into the dreaded "Decompression of svndiff data failed"
> problem.
>
> Running http://www.szakmeister.net/fsfsverify/utility trying to fix
> it I end up with a string of errors.
>
> So far I've seen:
> ------------
> - Error InvalidCompressedStream: Invalid compressed instr stream at
> offset xxxx (Error -3 while decompressing: incorrect header check)
> - Error InvalidCompressedStream: Invalid compressed data stream at
> offset xxxx (Error -3 while decompressing: incorrect data check)
> - Error InvalidWindow: The window header at offset xxx appears to be
> corrupted
> ------------

We have so far never been able to pin down the cause of such
corruption problems. It could be a bug in Subversion (and you should
be upgrading to avoid the ones that are already known), but it might
just as well be a bug in some dependency Subversion is using (such as APR),
or a bug in your operating system, or your disk controller or the disk
itself having problems.

If you'd like to share your corrupt revision file (privately if you like)
I'd be happy to take a look at it.
If you are lucky it's an instance of this problem:
http://subversion.tigris.org/issues/show_bug.cgi?id=3705
fsfsverify can fix some instances of this but not all.
I've fixed two such files manually so far which fsfsverify could not fix.

And even if it's something else, maybe we can figure out what went wrong.
And maybe if we see enough corrupt revision files we'll eventually be
able to pin it down to a bug in Subversion and fix it.

But the last time I was looking at a corrupted revision file it simply
contained corrupted zip data. zlib could not decompress it anymore
and nobody knew why. The file was simply broken and we could not
reconstruct it within reasonable effort.

So keep backups :)
Received on 2011-06-23 22:35:28 CEST

This is an archived mail posted to the Subversion Users mailing list.