Re: Some parts of repository corrupted - how to recover?

> Do you know what the contents of that file should be? (And do those
> contents match either of the checksums?)

There are two problem paths, and I had a working copy containing the
other one, so I got the checksum of that file and it matches the
recorded checksum in the repository. I.e. I think the checksums are
fine, it's the data which is wrong.

> If you can't get the contents, then make a copy of your repository,
> find the checksum in the db/representations representations table and
> edit it from
>
> 55b7db82c802ce6418b983e6ac27516c
>
> to
>
> 00000000000000000000000000000000
>
> Then try again (using the copy, of course). The all-zeros checksum
> always matches in Subversion.

Ok, not sure if I need a special BDB tool for this... I loaded the file
in a hex editor, and changed all four places where the string occurred
to zeros.

     $ svnadmin dump e:\svn > svn-dump-test
     * Dumped revision 0.
     ...etc...
     * Dumped revision 80.
     svn: Malformed skeleton data
     svn: Malformed representation skeleton

The last part of svn-dump test looks like:

     Node-path: compendium1/trunk/work/dump.pcx
     Node-kind: file
     Node-action: add
     Prop-content-length: 59

which is the name of the path that's not working. It looks like it
stops before it gets to "Text-content-length", "Text-content-md5", and
"Content-length".

So I'm assuming one of:
1. I should only have changed one or two of the places, or using a hex
editor isn't the right way.
2. I need to change something else, too.
3. Something else is corrupt.

>>Is this another use case for "svn obliterate" ?
>
> Nah, it's a case for finding & fixing the cause of the problem :-).

Yeah... the problem being the dodgy machine and the dodgy practices of
its owner, e.g. no backups!

> Oh, well, thanks, that's reassuring in a way... How can you work on a
> machine that randomly changes bits, man? :-)

Student = no money.

Thanks for help so far,
Edmund.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed May 14 04:24:36 2003