I'm fiddling with the README.txt file for the 1.2 Win32 binaries,
because I want to include instructions for upgrading BDB repositories
(1.1.x uses BDB 4.2, 1.2.x uses BDB 4.3). I've come up with the
following procedure:
----------
In this release, we've upgraded BerkeleyDB from version 4.2.52 to
4.3.27. If you are currently using Subversion 1.1.x as a server on
Windows with BerkeleyDB, use the following steps to upgrade your
repositories:
-- Make sure nobody is using the repository (stop Apache/svnserve,
restrict access via file://).
-- Using the old (1.1.x) binaries, run "svnadmin recover" for
each repository.
-- Using the new (1.2.x) binares, for each repository:
-- run "svnlook youngest"
-- run "svnadmin recover"
Once again, this is only necessary for repositories based on BDB.
You do NOT have to dump/reload your repositories.
----------
This seems to work in my tests. However, I'm seriously puzzled by the
need to run "svnlook" before "svnadmin recover" with the new binaries.
Recover by itself will choke, with the following error:
----------
Repository lock acquired.
Please wait; recovering the repository may take some time...
svnadmin: DB_RUNRECOVERY: Fatal error, run database recovery
svnadmin: bdb: Program version 4.3 doesn't match environment version
svnadmin: bdb: Skipping log file repo/db\log.0000000001: historic log version 8
svnadmin: bdb: repo/db\log.0000000002: log file open failed: No such file or directory
svnadmin: bdb: PANIC: No such file or directory
svnadmin: bdb: DB_ENV->log_put: 2: DB_RUNRECOVERY: Fatal error, run database recovery
----------
I'm inclined to call this a bug in svnadmin recover, but I'm not sure
how to start fixing it.
Any ideas?
-- Brane
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu May 5 00:41:27 2005