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

RE: Re: SVN commits fail- Can't get exclusive lock

From: Hila Afargan <HilaAfar_at_tauex.tau.ac.il>
Date: 2007-08-08 16:36:19 CEST


I eventually solved the locking problem!
The problem was with the NFS, and it affected the work with SVN, since
the repository is not local, but on a mount.
It was solved only after I rebooted the NFS server (and not just the
client, as I did before)

So simple, so annoying :)

Anyway, If someone will have this problem in the future,
I find another suggestion on this website:
"...changed the NFS mount option from default to
"hard,intr,bg,nolock,rw" and remount the nfs directory to my local mount


-----Original Message-----
From: Erik Huelsmann [mailto:ehuels@gmail.com]
Sent: Sunday, August 05, 2007 3:36 PM
To: Hila Afargan
Cc: Ryan Schmidt; users@subversion.tigris.org
Subject: Re: Re: SVN commits fail- Can't get exclusive lock

On 8/5/07, Hila Afargan <HilaAfar@tauex.tau.ac.il> wrote:
> Thank you, I checked and it does work if I use a repository on the
> local disk (for example in /tmp) even with my nfs user.
> My system is a nfs client.
> The repository is located on the nfs server disk, which is mounted to
> the my system.
> It used to work fine...
> Any ideas how to approach the problem?

I think c mike pilato already hinted you when redirecting you back to
users@ about this being an nfs problem where you need to run lockd for
an FSFS repository to work correctly. So, looking into running lockd and
using a server implementation which supports locks would be an idea...



To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Aug 8 16:34:44 2007

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.