upgrading SVN

["Woods, Jeff" <jw...@sfwmd.gov>]

As a result of upgrading from RHEL 3 to RHEL 4, my Berkeley database
libraries have been upgraded from 4.1.25 to 4.2.52 and subversion was
upgraded from 1.0.9 to 1.1.4.
 
Since our repository is only lightly used, everything appeard to be okay
at first.  Soon, though, we began seeing reports of corruption.  Fearing
that this may be due to an incompatibility in the BDB file formats, I
used the old db41 utilities to dump the databases, and then imported
them into fresh 4.2 format (the full process I used is documented at
http://svn.haxx.se/users/archive-2004-09/1184.shtml).
 
Everything exported and imported without mention of an error, and
(again!) everything looked okay.  I was able to check out a complete
copy of the tree and was able to make commits after the dump/import
process.  A few days later, we began getting a new error:
 
     svn: Commit failed (details follow):
      svn: Berkeley DB error while checkpointing after Berkeley DB
transaction for filesystem /u02/svn/rsmgui/db:
      Invalid argument
      svn: bdb: Ignoring log file: /u02/svn/rsmgui/db/log.0000000001:
magic number 0, not 40988
      svn: bdb: DB_ENV->log_put: 1: Invalid argument
      svn: bdb: txn_checkpoint: failed to flush the buffer cache Invalid
argument
      svn: Your commit message was left in a temporary file:
      svn:
'/nw/oom/sfrsm/workdirs/brhammon/work/rsmpost/svn-commit.tmp'

This appears to be a problem with the log file created with the BDB
environment.  Has anyone seen this sort of problem before?  If so, is
there a resolution?

Re: upgrading SVN

[Bob Proulx <bo...@proulx.com>]

Woods, Jeff wrote:
> This appears to be a problem with the log file created with the BDB
> environment.  Has anyone seen this sort of problem before?  If so, is
> there a resolution?

Generally there have been problems of the sort you mention with the
BDB.  The sentiment from many is that the BDB should be dropped
entirely, although others disagree.  Some people use it without
trouble while others are plagued with problems.

Since you are having trouble with the BDB then consider converting
your backend to fsfs instead.  Dump and load your database and create
a new one using the fsfs instead.  I am using the fsfs exclusively.
Using the fsfs backend will avoid the problems you are seeing.

Bob

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org