Re: Rescuing a repository

On Monday 17 May 2004 17:03, kfogel@collab.net wrote:
> Marc Haisenko <haisenko@webport.de> writes:
> > I do have one suspect, but I'd like to verify that one for sure,
> > I'll tell you tomorrow whether I was right or not ;-)
>
> Thanks -- will watch for the post.

Okay, so what I've found is a bit weird:
I suspected that the corrupt revision is caused by one or more of the three
files that were added in that corrupt revision. And really looks like that,
but isn't reproducable every time:

I created a new repository and loaded the dump up to one revision before the
corrupt one. I checked that repository out and added the files that my logs
said were added in the corrup revision. I did a repository dump, everything
went fine, then committed the three files (commit didn't give any error
messages) and did another repository dump:

svn: Checksum mismatch on rep '4ph':
   expected: eff6610598f05746eecd37c54f9ad706
     actual: 584136babe24324accc8b5bbb693dbdb

Here we go again. I then tried to narrow it down to which file was causing the
problem, so I recreated the repository as described above, checked it out and
only added one of the three files. I did this for all three files and the
dumps went fine.

I was very surprised by that and tried the first test (which triggered the
checksum mismatch) again, this time the dump went fine. So I can't reproduce
this all the time :-(

And to make matters worse, testing takes a long time as the repository is
quite big, and I don't think I can send you the files which triggered the
error (I have to talk to my boss, but he's out of town for a few days... I
hope I don't forget asking him).

C'ya,
        Marc

-- 
Marc Haisenko
Systemspezialist
Webport IT-Services GmbH
mailto: haisenko@webport.de
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org