[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

svnadmin dump || hotcopy : Program version matching error

From: <Nicolas.Castagne_at_imag.fr>
Date: Thu, 15 Oct 2009 17:06:11 +0200 (CEST)

Hi there,

I am starting to administrate a series of svn repositories, and face
problem when trying to dump or hotcopy them.

Problem report
% sudo svn dump /path/to/my/repository
% sudo svn hotcopy /path/to/my/repository
I get the (usual?) error:
svn: Berkeley DB error while opening environment for filesystem 
Argument invalide
svn: bdb: Program version 4.2 doesn't match environment version
A weird (?) thing is the fact that everything runs smooth (eg : svn co,
svn up, svn commit, svnadmin create, etc.) appart these commands...
This may be strange, since the problem report I read on the Net explain
that most svn commands are broken when having a berkeley DB version
I do know that this error is quite common. But I did not find an
appropriate HOWTO for a svn administror newbee like myself :( Sorry for
Here are some details on my config :
   svn version                            1.1.4 (quite old indeed !)
   db schema format of my repositories    3
   berkeleydb version (eg db4.2_archive)  4.2
The db format of my repository is      3
Here we go.
Question 1
Since svnadmin dump||hotcopy do not work, What should I do to secure this
important repository before I change anything on it, or before I upgrade
anything in svn ?
Is copying (cp -r) the repository sufficient in such a case ?
Question 2)
The problem should be related to the DB schema version of my repository,
as compared to the schema version of the svn binary (or berkeley db
A weird thing, here, is that the server has NOT been upgraded since the
repository has been created (at least for one of them).
Do you see an explenation to this ?
Question 3)
Apprently I should "upgrade my repository", as explained in various
places, eg http://svn.collab.net/repos/svn/trunk/notes/repos_upgrade_HOWTO
Is that correct ?
The upgrade process requires using an old binary of svnadmin with the same
schema version as my repository (3 in my case).
Well OK.
But how can I know which svn version is OK for this ?
And how may I get it and install it ?
I thank you much for your answers.
And sorry for this (not new) question...
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-10-15 17:45:45 CEST

This is an archived mail posted to the Subversion Users mailing list.