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

Re: Fixing commit/import error

From: Hari Kodungallur <hkodungallur_at_gmail.com>
Date: Sat, 29 Aug 2009 12:03:55 -0700

On Sat, Aug 29, 2009 at 8:08 AM, Rich Shepard <rshepard_at_appl-ecosys.com>wrote:

> I've not worked on a project since before upgrading my distribution
> (Slackware) earlier this year. Yesterday I went back to the project and
> ensured it still worked with upgraded tool versions. It does. However, when
> I tried to commit the changes the attempt failed:
> [rshepard_at_salmo /data1/eikos]$ svn commit -m "New python, wxPython
> versions."
> svn: Commit failed (details follow):
> svn: Unable to open an ra_local session to URL
> svn: Unable to open repository 'file:///usr2/svn-repos/eikos/trunk'
> svn: Berkeley DB error for filesystem '/usr2/svn-repos/db' while opening
> environment:
> svn: Cannot allocate memory
> svn: bdb: unable to allocate memory for mutex; resize mutex region
> I could not find any help in Mike Mason's "Pragmatic Version Control
> Using
> Subversion" which I've had since it was published in 2005.

This is a bdb issue. Bdb must have got upgraded along with the slackware
upgrade. But the data was created using old version of bdb.
May be this thread that I found after googling might help:

You you could just dump the data (svnadmin dump) and then load it into a new
FSFS repository. This way it is not dependent on BDB anymore.

> The repository no longer has a directory for this project (named
> 'eikos'):
> [rshepard_at_salmo /data1/eikos]$ ls /usr2/svn-repos/
> README.txt conf/ dav/ db/ format* hooks/ locks/

This is alright. All the information regarding the directory structure is
within the database.

> so I tried to re-import the project and start counting versions again.
> That,
> too, failed for the same reason. However, in the project directory's
> .svn/entries I see data that appears to span the years I worked on the
> project.
  I would greatly appreciate help in learning what broke and what I do to
> fix the problem(s) so I can once again use subversion-1.5.7, currently, for
> this project.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-08-29 21:04:51 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.