Nathaniel Irons wrote:
> I'm running svn 1.0.5 on Mac OS X 10.3.4, BDB 4.2.52, no fink,
> single-user svnserve/svn+ssh setup, light use. Commits recently began
> resulting in checksum errors:
> Transmitting file data ...svn: Commit failed (details follow):
> svn: Base checksum mismatch on '/project/trunk/<filename>.h':
> expected: e5e97e6749bcd42073e2f4669f701035
> actual: 95d4650ff827732683a8763075af693f
> Updates result in even less helpful errors:
> svn: Reference to non-existent revision '65' in filesystem
> My archive of these lists only goes back a couple of months, and the
> mailing list search is mostly erroring out, so I've only tried a handful
> of things:
> * "svnadmin recover" told me everything was fine, and had no effect.
> * "chmod -R 777 /Library/svnrepo/" had no effect
> * "svnadmin dump" dies almost immediately:
> $ svnadmin dump /Library/svnrepo/ > repo2
> * Dumped revision 0.
> * Dumped revision 1.
> svn: Checksum mismatch on rep '8':
> expected: 3d4537ff611761accd555d157ce3efcc
> actual: 6558074509e0288f0ecea8329f839993
> * Identical checksum errors to the above result from running "svnadmin
> verify" on a repository copy.
> * db_recover:
> $ /usr/local/BerkeleyDB/bin/db_recover -c -v [in /db/ of repo copy]
> db_recover: Finding last valid log LSN: file: 6 offset 167255
> db_recover: Recovery starting from 
> db_recover: Recovery complete at Sat Jul 31 20:05:23 2004
> db_recover: Maximum transaction ID 80003800 Recovery checkpoint
> After running db_recover, "svnadmin verify" again dies at the same
> checksum error as svnadmin dump.
> I won't lose anything critical if I can't restore this, as I was really
> just getting my feet wet, but I'd be pleased to recover the commit
> notes. Any suggestions would be appreciated.
Something pretty bizarre has happened to this repository.
Would you be able to put a tarball of the repository on a web/ftp site and
email me the URL?
I'll assess the damage and try to recover.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Sun Aug 1 18:20:40 2004