Ryan Schmidt wrote:
> On Oct 5, 2005, at 16:38, Mattias Brändström wrote:
>
>> Unfortunately I have not been able to get subversion to say
anything more than this. If I try to issue the same commit command
again I get this error message:
>>
>> svn: Commit failed (details follow):
>> svn: Berkeley DB error for filesystem /home/svn/business-server/db
while opening environment:
>> DB_RUNRECOVERY: Fatal error, run database recovery
>> svn: bdb: PANIC: fatal region error detected; run recovery
>> svn: Your commit message was left in a temporary file:
>> svn: '/home/mattias/tt-projects/business-server/trunk/svn-commit.
4.tmp'
>>
>> If I run 'svnadmin recover' and commit again I get the first error
message again. More information about my specific setup below:
>>
>
> Can you svnadmin verify, or svnadmin dump?
>
> If verify shows a problem with a revision, maybe we can figure out
what's wrong with that revision. If verify shows no problems, then you
should also be able to dump, and if you can do that, you should be able
to import into a new repository.
>
This was really, really nice advice! Thank you!
Both 'svnadmin verify' and 'svnadmin dump' ran fine without any errors.
I didn't know that these commands existed. By using 'svnadmin dump' and
'svnadmin load' I have managed to get a repository that, to my untrained
eye :) , looks just like the old repository.
As soon as I find the time I will follow your other advice and switch to
an FSFS backend.
:.:: mattias
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Oct 5 18:32:57 2005