RE: "Decompression of svndiff data failed"

I just use a shell script:

REPO=$1

REV=$2

/opt/ptc/bin/fsfsverify.py -f
/opt/ptc/subversion/sets/$REPO/db/revs/$REV

/opt/ptc/bin/fsfsverify.py /opt/ptc/subversion/sets/$REPO/db/revs/$REV

until [ $? -eq 0 ]

do

  /opt/ptc/bin/fsfsverify.py -f
/opt/ptc/subversion/sets/$REPO/db/revs/$REV

  /opt/ptc/bin/fsfsverify.py /opt/ptc/subversion/sets/$REPO/db/revs/$REV

done

From: Robert Dailey [mailto:rcdailey_at_gmail.com]
Sent: 31 March 2009 17:29
To: Watson, Chris
Cc: Christian Unger; users_at_subversion.tigris.org
Subject: Re: "Decompression of svndiff data failed"

Any ideas on this guys? Sorry to rush but I *really* need to get this
fixed.

On Mon, Mar 30, 2009 at 1:37 PM, Robert Dailey <rcdailey_at_gmail.com>
wrote:

Actually no, the offset is not the same. The offset now is 16102919.

Why is this happening? Can't I tell fsfsverify to just fix *everything*
instead of constantly having to run it to fix every single offset?

On Mon, Mar 30, 2009 at 3:39 AM, Watson, Chris <cwatson_at_ptc.com> wrote:

Is it the identical error? Or a minor variant? - e.g. is the offset
exactly the same?

I find that I need to run fsfsverify multiple times to fix each error.
It doesn't fix all the errors but only the first one it finds.

If it is the same error then you are pretty screwed. The only way that
I've ever found forward is to use svnadmin dump/load to recreate a
repository with everything up to the break, then do an svn co of the
damaged revision and pull out everything up to the fault, and then use
svn cat to pull out everything after the fault that you can. Then you
need to get new copies of the damaged file and recreate the revision -
you can then reapply the newer revisions on top with svnadmin dump/load

Chris

From: void pointer [mailto:rcdailey_at_gmail.com]
Sent: 28 March 2009 20:04
To: Christian Unger
Cc: users_at_subversion.tigris.org
Subject: Re: "Decompression of svndiff data failed"

On Fri, Mar 27, 2009 at 5:16 PM, Christian Unger
<christian.unger_at_me.com> wrote:

try this:

http://www.szakmeister.net/fsfsverify/
<http://www.szakmeister.net/fsfsverify/>

Thanks Christian.

I tried doing as you stated and I get the following when I run
fsfsverify without the -f option:

Error InvalidCompressedStream: Invalid compressed instr stream at offset
16102916 (Error -3 while decompressing: incorrect header check)

Try running with -f to fix the revision

When I run it with -f, it says it fixed it and to run fsfsverify without
the -f option to double check. When I run without -f the second time, I
get the very same error again as above.

Am I completely screwed?

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1499084

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-03-31 21:51:01 CEST