"Checksum mismatch" following upgrade to 1.2

Hi all,

I upgraded to subversion 1.2 (and went through the BerkeleyDB
upgrade to 4.3 "recovery" process described at the subversion site).
  Now commits fail with checksum mismatch errors. An "svnadmin
verify" gets all the way to revision 6 (out of over 200) before
cratering with another checksum mismatch.

It seems pretty clear that the transition to the 4.3 database
corrupted my repository. The repository traffic is extremely light
(I'm the only one using it for generally (very) small commits) and
all via file:///), so I'm having a hard time accepting that this is
result of intense usage or mixed network/file access.

Is there a way to repair the repository?

Thanks very much,
Dave
 

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Jul 3 05:26:07 2005