Recovering from bad dump

John,

thanks for replying.

I tried zeroing the checksum, but it didn't seem to work. What exactly
should it be set to?

The lines at present are something like

Text-content-length: 16904
Text-content-md5: 6d22a1da5cd863e908d36f97bf8b2fb5

At this stage, it seems that the problem is with the checksum, so I want to
try the load. I have only the dump file, not the repository.

If I try setting the schecksum in the dump to zeroes it does not work:

svnadmin: Checksum mismatch, file '/website/bloxsom/blosxom.cgi':
   expected: 00000000000000000000000000000000
     actual: 6d22a1da5cd863e908d36f97bf8b2fb5

On 19/04/06, John Szakmeister <john@szakmeister.net> wrote:
>
> On Sunday 02 April 2006 22:22, Martin Ellison wrote:
> > I have an svnadmin dump file which is showing checksum errors when I
> load
> > it into a new repository on a new server. Unfortunately, I do not have
> > access any more to the original repository and I need to recover to a
> new
> > server. Attempts to recover on a file-by-file basis by hacking the dump
> > file are now resulting in "File not found" errors.
> >
> > What I need is something to recover as much as possible from the dump
> > file, even if it means losing a few files (mainly , I want the text
> files,
> > and all the files that are causing the problems are binaries).
> >
> > Is there any way of fixinf this such as a "--force" option on the load
> or a
> > cleanup program that creates a clean dump file?
>
> There is no such option currently. If it's only showing checksum errors,
> then
> the easiest thing to do is zero the md5sum. All zeroes is a wild card
> that
> will always match. However, it may also mean your files are really
> corrupted, so you'll want to go back and make sure that things look good.
>
> -John
>

--
Regards,
Martin
(m.e@acm.org)
--
Regards,
Martin
(m.e@acm.org)