Mathieu MERLAY wrote:
> I need to transfer my SVN repository on a new server, that's why I would
> like to dump my current repository tree.
> I tried svnadmin dump "directory" > "file".
> Revisions to 110 are correctly dumped, but on the 111, I've this message :
> * Dumped revision 110.
> * Dumped revision 111.
> svn: Checksum mismatch on rep '18t':
> expected: 8cc04ee47694ad36e632a5acbc906d07
> actual: 2a2eb00769b48989502df3a5c1b346f2
> zsh: exit 1
> Today, the repository is at revision 262 and updates/commits are working
> very well.
> The computer is a single CPU Pentium MMX under Debian/Linux (woody) with
> subversion packages from backports.org. The repository was created under
> version 0.7.0, and is today under 1.0.5.
> I've already seen questions about this failure, but I've never found an
> answer to correct this. Maybe can we change the checksum in the database
> ? I would like to transfer this repository as soon as possible.
> Thank you for your help
At one point, way back in 0.24 days, I ran into a similar problem, but
short of sending in my repository for manual fixing (which my superiors
wouldn't let me do) I was unable to correct this.
However all was not lost. I *was* able to do an export successfully on
this repository and recover all data OK, and re-import to a newer
version, losing the log information on changes. Well, that is not
exactly correct either as I've kept an old copy around with the old
repository, for the odd time (happened once now in 6 months) that
someone needed to find a reason for a prior change.
I have also come to the conclusion (but do NOT have any proof) that the
corruption occurred because of accessing the repository using both svn
and http simultaneously (and erroneously), perhaps even when doing a
recovery operation. Was involving a directory that was deleted via one
mechanism. Won't do that again needless to say.
The svnadmin dump continued to fail even after catastrophic db recovery
attempts, which is what led me back to the export, which succeeded with
no failures or data loss of any kind.
Don't know if it helps or not....
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Wed Jun 16 19:01:19 2004