Svnadmin verify gives checksum error - now what?
From: Jeff Rivett <jrivett_at_uvic.ca>
Date: 2005-09-09 00:41:59 CEST
Hello all -
I'm using Subversion 1.2.1 on Windows (yes, I know: ugh). Basically everything was fine until I installed 1.2.1 in July. Yesterday I started seeing errors in one repository. Noticing that the main DB file for that repository was over 4GB, I started doing some research. Eventually I found an alert about the LIBDB43.DLL version problem and downloaded the patch.
Now I figured that the repository was corrupt and in fact no amount of "svnadmin recover" or "db_recover" brought it back to life. So I restored from backup.
Problem #1: My working copies now don't match the repository. When I try to check for modifications, I get a "version mismatch" error. Which makes sense; the working copy has a bunch of revisions that the restored repository does not. But how do I reconcile the working copy with the restored repository?
Problem #2: I figured I should verify the repository. "svnadmin verify" zips along fine until the final revision, at which point it says "Checksum mismatch on rep 'c3u': expected ___, actual ___. What the heck is 'c3u'? And how do I fix this problem?
Regards,
Jeff Rivett
---------------------------------------------------------------------
|
This is an archived mail posted to the Subversion Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.