Marc Haisenko wrote:
> ...
> I then ran 'svnadmin dump /export/rescue', and everything went fine until it
> reached revision 336 where a checksum mismatch was reported. Repeatedly
> running the dump always yields the exact same checksum mismatch (always the
> same checksums).
>
> I suspected a defect RAM, installed Memtest86 and ran it but after letting it
> run through the night no defective RAM was found.
> ...
Hi Marc, I've been in exactly the same situation (well, apart from not
worrying about a boss and it being a much smaller repository). In my
case the cause was defective RAM (which, btw, I'm still using ;-).
--> The first thing to do is figure out which node is causing the
checksum error. This can usually be done by looking in the dump output
for the last node header mentioned. If the Text-Content-Length is
smaller than the bytes output after that header (after the PROPS-END
line), then that node is giving the MD5 error).
When this happened to me the dev@ people suggested I edit nodes to set
the checksum for that node to 0000....... as this checksum matches any
data. You'll probably lose that node, of course, but at least you'll be
able to dump all the remaining nodes.
(If you get the same problem later on in the dump -- perhaps there's
another node that has a diff against the corrupt one; perhaps there's
another corrupt node -- repeat from the line marked -->).
You might want to ask "how do I edit the checksum?" to which someone
other than I can probably give a more helpful answer. :-)
Hope this helps,
Edmund.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri May 14 15:05:30 2004