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.
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.
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).
Not a Gentoo-specific issue, needs to be fixed upstream.
