On 03/25/2014 12:30 PM, Bert Huijben wrote:
> On the OpenBSD bot I see a BDB test failure.
> svn_tests: E170013: Unable to connect to a repository at URL
> svn_tests: E180001: Unable to open repository
> subversion/libsvn_fs_base/fs.c:611: (apr_err=SVN_ERR_FS_BERKELEY_DB)
> svn_tests: E160029: Berkeley DB error for filesystem
> test-work/repositories/repo_wc_copy-2/db' while opening environment:
> subversion/libsvn_fs_base/bdb/bdb-err.c:62: (apr_err=SVN_ERR_FS_BERKELEY_DB)
> svn_tests: E160029: Invalid argument
> subversion/libsvn_fs_base/bdb/env.c:230: (apr_err=SVN_ERR_FS_BERKELEY_DB)
> svn_tests: E160029: bdb: DB_REGISTER limits processes to one open DB_ENV
> handle per environment
> FAIL: op-depth-test 88: repo_wc_copy
> This error is caused by copying the entire repository to a new location and
> then relocating a working copy to the new location.
> I would say that there must be some supported way to do this from the test
> suite, but:
> * I can't move the repository (as there are open files)
> * I can't hotcopy the repository (that somehow hangs)
> * And copying doesn't work either... see this error.
> Any BDB experts around that can find a way how to fix this?
It is definitely a requirement of our BDB integration that a given
process only attempt to hold open a single connection to the Berkeley DB
environment at a time, and it is the DB_REGISTER subsystem which
enforces that. I assume that what's happening is that your process
opens the original repository, copies the repository (which carries with
it the db.register file), and then upon trying to open the copied
repository runs into problems because BDB sees the PID in the
db.register file already. If this is the case, the solution should
simply be to ensure that you don't have the original repository open at
the time you copy it.
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet <> www.collab.net <> Enterprise Cloud Development
Received on 2014-03-25 18:24:54 CET