Bug 73590

Summary:	subversion 1.1.1-r3 and db-4.1.25_p1-r4 unable to read repository
Product:	Gentoo Linux	Reporter:	Billy Holmes <billy>
Component:	[OLD] Development	Assignee:	Paul de Vrieze (RETIRED) <pauldv>
Status:	RESOLVED UPSTREAM
Severity:	normal
Priority:	High
Version:	unspecified
Hardware:	All
OS:	All
Whiteboard:
Package list:		Runtime testing required:	---

Description Billy Holmes 2004-12-06 14:13:37 UTC

After updating subversion to 1.1.1-r3 and db-4.1.25_p1-r4, I was unable to read my repositories. I was able to read the repository the previous day, prior to the update. 

The error is as follows:
$ svn co file:///home/repos/booking booking
svn: Unable to open an ra_local session to URL
svn: Unable to open repository 'file:///home/repos/booking'
svn: Berkeley DB error while opening environment for filesystem /home/repos/booking/db:
Resource temporarily unavailable
svn: bdb: unable to join the environment

In order to fix I had to:

$ svnadmin recover /path/to/repository

then I could checkout the repository.

This affected all repositories and all functions of the repository, even those repositories which had not been touched in months.

Comment 1 Paul de Vrieze (RETIRED) gentoo-dev

2004-12-08 03:09:13 UTC

The change of db version is often very problematic. The safest course of action when updating the db version is to dump the repository and reload it. db is supposed to have upwards compatibility but that doesn't really work.

Comment 2 Maxwell Grender-Jones 2005-06-01 03:31:02 UTC

fwiw, I'd recommend using svnadmin create --fs-type fsfs /path/to/repo to create
your repository, as it avoids all the pain that is incompatible db versions (by
not using db).

Comment 3 Jakub Moc (RETIRED) gentoo-dev

2005-12-06 19:23:06 UTC

Not a Gentoo-specific issue, needs to be fixed upstream.