On Sat, Dec 11, 2010 at 12:47:40AM +0000, stuart wrote:
> >svn ci -m "svn lock trouble" .
> svn: Commit failed (details follow):
> svn: Can't get exclusive lock on file
> '/media/stuart/svn/ca/db/txn-current-lock': No locks available
>
> I had done a svn mkdir and svn moved a bunch of files to it plus adding
> some more - is that relevant?
>
> I tried a
>
> svn ci .
>
> but the program hung after the edit pop up, and I killed it.
>
> Since then I can not get it past the No locks available message.
>
> I have tried all the possible relevant admin actions I could find in the
> manual, including recover (which also dies for lack of lock).
>
> lslocks does not show any
>
> rmlocks does nothing
These subcommands don't have anything to do with the txn-current-lock
file. The lock you see failing serializes multiple server threads trying
to perform commits in parallel. It's not a lock which Subversion users
can see or control.
> svn status -u sees no problem
Yes, because it doesn't try to commit.
> and so on.
>
>
> I am running Ubuntu 10.10 Maverick Meerkat and the distribytion is up to
> date.
This could be a file permission problem on the server side.
Does the server process have necessary permissions to open or create
the file db/txn-current-lock?
Stefan
Received on 2010-12-16 19:39:24 CET