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

Re: a non-atomic svn commit - possible bug?

From: Bryan Donlan <bdonlan_at_hikari.afraid.org>
Date: 2005-02-09 20:13:38 CET

Hash: SHA1

Toby Johnson wrote:
| Max Bowsher wrote:
|>> /* tail-end of "svn commit" output below (path names changed) */
|>> Transmitting file data ..........svn: Commit failed (details follow):
|>> svn: Berkeley DB error while appending string for filesystem
|>> /path/to/repos/db:
|>> Not enough space
|>> svn: bdb: Lock table is out of available locks
|>> svn: Your commit message was left in a temporary file:
|>> svn: 'svn-commit.tmp'
|>> # echo $?
|>> 1
|> Sounds to me like the commit was successfully atomically applied, but
|> then an error occurred whilst deltifying old versions of the files
|> against the new fulltexts.
| So what exactly does this mean to us non-SVN hackers? Is the repository
| in a usable state at this point? Is this something to watch out for? How
| does one recover from this situation?

I'm not sure, but I think it means the commit did succeed, but some
internal bookkeeping failed afterward. I'm not sure, but I think this
will fix it:

* Shut down all accessors
* svnadmin recover (repo)
* svnadmin deltify (repo)
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Feb 9 20:15:59 2005

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.