Hi
I recently downgraded from berkeley db4.1 to the suggested db version 4.0.
The only way i found to migrate my existing repos to the subversion server
was to dump the repositories and load them back into the new subversion.
Dumping and loading was working w/o errors, when i listed the root
directory of a repos the first time it was shown normally, but when i
relisted the same repos a second time the db_runrecovery error came up. I
was not able to recover the repository after that, i had to load from dump
again. Right after loading I ran 'svnadmin recover' on it and tried listing
again (and again, and again ;-)) - the repository is now working as
expected. Running 'svnadmin recover' after the first 'svn ls' works too -
but it fails after I listed the repos a second time.
example output of 'svnadmin recover' after loading - there seems to be no
error
# sudo -u apache svnadmin recover test
Acquiring exclusive lock on repository db.
Recovery is running, please stand by...
Recovery completed.
The latest repos revision is 7.
I reproduced that on all 4 repositories i migrated. What i found strange
was that _listing_ the repositories content can crash it.
I found no issue about that on your issuetracking page, i think this a bug
- unless somebody here has a good idea what i could have done wrong, or
what i can try to work around that problem. My repositories work now, but
just dumping/loading them was not enough.
Yours
Mike
p.s.: i'm not subscribed to the list, please add me to CC when answering.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jun 30 22:28:30 2003