Kenneth Jensen wrote:
> I have been committing my masters thesis to a partially corrupt
> repository for a few days now, only just discovering it today. :(
> When I try to checkout or update i get the message:
> svn: Checksum mismatch on rep '3h':
> expected: 241309c1a14a94940f57af83d76038d8
> actual: c6838e324679044d56ac1217df9036ec
> But if I run verify or dump I get this:
> * Verified revision 0.
> svn: Checksum mismatch on rep '0':
> expected: 5bbf6a265ebefcae6fd4da35458fefcf
> actual: 7a118105e6c365008af862a184214cfe
> I asked the almighty Google, and tried some of its recommendations.
> Thus running a svnadmin recover on the repository gives this:
> Repository lock acquired.
> Please wait; recovering the repository may take some time...
> Recovery completed.
> The latest repos revision is 116.
> This looks fine, except it doesn't change much.
> When I committed my changes yesterday, I didn't get error messages,
> and the revision bumped 1 up, as expected. Although the svn status did
> show a few !-marks...
> I have a cron job that takes a full dump of the repo every night (only
> a few MB's), and I can see that the last successful dump was the 26.
> of april, and the rest of the dumps are only few bytes long. This
> kinda sucks, since the thesis is due in less than a month - don't
> really need to learn too much about versioning tools right now. :-)
> Does anybody have hints to how I restore the sanity in my repo? Or
> should I just throw it out, load the last backup and commit my local
> changes? I won't miss any work, but lose the history of the last week
> or so.
I suggest finding the highest revision number in your last good dump, then
svnadmin dump --incremental -r <that-revnum-plus-1>:head myrepos >
If that works, you can then load your backup, and myextradump, one after
the other into a new repository.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Wed May 4 22:54:05 2005