You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Nicholas Walker <NW...@dialogue-marketing.com> on 2009/04/02 20:31:35 UTC
Help with corrupted repository
I have a repository that has been around for about 7 years without being
actively maintained. We're trying to migrate the repository to a
different server, and clean up the repository.
When doing an svnadmin dump or verify, there are 38 revisions that
report a checksum mismatch. The repository is using Berkeley DB. I
have tried skipping the revisions, and loading into many different dump
files, and then re-loading, but some of the skipped revisions are
referenced by other revisions, and re-loading generates an error.
I have found some possible work around's using the fsfs db, but can't
find a way to repair a Berkeley db.
We are running currently version 1.4.4.
I have searched google endlessly for two days trying out different
things but I haven't been able to find a resolution.
Is there any way for svnadmin dump to ignore the fact that there was a
checksum failure, or anyway to modify/repair the revision in Berkeley
Db?
I would appreciate any ones help in pointing me in the right direction.
Thanks,
Nicholas Walker
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1524044
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].