Thank you for your help.
I changed the permissions on the repository but it didn't help.
We do use NFS in our system, daemon [lockd] is currently running.
I created new repository in my home directory:
> svnadmin create my_repo
>mkdir proj/branches
>mkdir proj/tags
>mkdir proj/trunk
>touch proj/trunk/foo.c
> svn import proj file:///usr/users/hilaafar/my_repo -m "initial import"
Adding proj/trunk
Adding proj/trunk/foo.c
svn: Can't get exclusive lock on file
'/usr/users/hilaafar/my_repo/db/transactions/0-1.txn/rev-lock': No locks
available
Same error message, this time with import!
What should I do?
Hila
________________________________
From: nick_stolwijk@planet.nl [mailto:nick_stolwijk@planet.nl]
Sent: Wednesday, August 01, 2007 3:45 PM
To: Hila Afargan; users@subversion.tigris.org
Subject: RE: RE: SVN commits fail- Can't get exclusive lock
I've found another usergroup posting:
On Wednesday 20 December 2006 17:34, Bryan Linkous wrote:
> I have an FSFS style repository that is share over NFS. When I try to
> commit to a particular project in the repository, I get the following
> message:
>
> Transmitting file data ..svn: Commit failed (details follow):
> svn: Can't get exclusive lock on file
> '/data1/subversion/repo/db/write-lock': No locks available
Make sure the directory /data1/subversion/repo/db/ is read, write, and
executable for you.
> I can commit and check out other projects without any problems.
Are these on the same NFS share?
Yes: it is probably the permissions.
No: it could also be that the lock-daemon is not running on the
NFS-server,
ask your admins. (If you are the admin and you don't know what lockd is:
call your system support guy.)
Konrad
Maybe this is your problem?
Hth,
Nick Stolwijk
-----Original Message-----
From: Hila Afargan [mailto:HilaAfar@tauex.tau.ac.il]
Sent: Wed 8/1/2007 2:30 PM
To: nick_stolwijk@planet.nl; users@subversion.tigris.org
Subject: RE: RE: SVN commits fail- Can't get exclusive lock
Thanks you, but no, we have enough disk space.
I suspect that the problem begun after the last REBOOT of the system,
If it helps.
________________________________
From: nick_stolwijk@planet.nl [mailto:nick_stolwijk@planet.nl]
Sent: Wednesday, August 01, 2007 3:07 PM
To: Hila Afargan; users@subversion.tigris.org
Subject: RE: SVN commits fail- Can't get exclusive lock
A few days ago, we had also such an issue, and it turned out, that our
disk was full. Maybe that's also your problem?
With regards,
Nick Stolwijk
-----Original Message-----
From: Hila Afargan [mailto:HilaAfar@tauex.tau.ac.il]
Sent: Wed 8/1/2007 2:03 PM
To: users@subversion.tigris.org
Subject: SVN commits fail- Can't get exclusive lock
Hello,
we can't make any commit commands to our SVN repository (running SVN on
Red Hat Enterprise Linux 4) .
We tried different users on files, and all commit commands failed.
Here is an example:
> svn commit -m "No real change" mainSemphy.h
Sending mainSemphy.h
Transmitting file data .svn: Commit failed (details follow):
svn: Can't get exclusive lock on file
'/SVN/db/transactions/2323-1.txn/rev-lock': No locks available
> svn status --show-updates
M 2323 mainSemphy.cpp
M 2323 mainSemphy.h
Status against revision: 2323
We tried to check if there are any locks:
> svnadmin lslocks /usr/users/evolution/pupkoSVN
didn't return any output. So we don't really have any locks. Could it be
some other issue?
We also run a recovery which worked ok:
> svnadmin recover /usr/users/evolution/pupkoSVN
Repository lock acquired.
Please wait; recovering the repository may take some time...
Recovery completed.
The latest repos revision is 2323.
But we still can't Commit?
Other commands, such as Update does work.
Thanks for your help.
Hila
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Aug 2 15:03:48 2007