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

Re: "{svn | svnadmin}: Decompression of svndiff data failed" and "svn: Malformed representation header", "svn: Corrupt representation" messages

From: Daniel Shahaf <danielsh_at_elego.de>
Date: Thu, 21 Apr 2011 16:13:47 +0300

Bastian Ugimachi wrote on Thu, Apr 21, 2011 at 14:52:33 +0200:
> 2011/4/21 Daniel Shahaf <danielsh_at_elego.de>
> > Bastian Ugimachi wrote on Thu, Apr 21, 2011 at 14:17:00 +0200:
> > > The intersting thing is that the ID in my error message belongs does not
> > > belong to the same representation as the part extracted by xxd around the
> > > specified bytes...?!
> >
> > Well, it's corrupted. The correct representation might be somewhere
> > nearby --- perhaps a few hundred bytes away (in either direction)?
> >
> Is there any chance to make this consistent again?

Yes, with a bit of skill and luck. Do you have a working copy of r2?
Does the rev file contain all the information (just possibly in the
wrong place)? Do you have backups?

The solutions I'm getting at are "manual revision file surgery/reconstruction".
(You may be able to do it yourself if you study the 'structure' file and
have some patience.) There may be other classes of solutions.

> And where could this inconsistence possibly come from?

"Bug in libsvn_fs_fs". (See issue #3705.) Or bug in any of N other
things, including but not limited to hardware bugs.

By the way: did you say what version of svn your server was running?

> By the way, I just remarked, that "svnadmin verify ...-r x" is wrong ONLY
> for x=2, not for x>=2 as I wrote before. So correcting this one should make
> the repository be OK again, I guess?

Yes. I'd expect verify to fail only for r2, but checkout to fail for
(at least some) later revisions as well.
Received on 2011-04-21 15:14:58 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.