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

Re: svn commit bug over NFS

From: Nelson Elhage <nelhage_at_MIT.EDU>
Date: 2007-03-27 16:57:35 CEST

Ah, thanks for the pointer. Some googling reveals that lockd is not
supported by the userspace NFS server, which is what I had been
running. Switching over to the kernelspace server appears to have
resolved the issue.

Thanks for looking into, and sorry for bothering you with an unrelated

- Nelson Elhage

On Tue, Mar 27, 2007 at 10:11:09AM +0200, Erik Huelsmann wrote:
> On 3/27/07, David Glasser <glasser@mit.edu> wrote:
> >On 3/26/07, David Glasser <glasser@mit.edu> wrote:
> >> On 3/26/07, Nelson Elhage <nelhage@mit.edu> wrote:
> >> > Transmitting file data .svn: Commit failed (details follow):
> >> > svn: Cannot write to the prototype revision file of transaction '14-1'
> >because a previous representation is currently being written by another
> >process
> >>
> >> One question: is the transaction id (14-1) consistent?
> >
> >Ah, I guess it make sense if it does because from the strace it looks
> >like it cleans up the entire transaction after it fails.
> >
> >The key line seems to be:
> >
> >fcntl64(6, F_SETLK, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}) =
> >-1 EACCES (Permission denied)
> >
> >I know very little about NFS... do you need to specially allow users
> >to lock files (like in AFS)?
> I think you need to run the locking daemon lockd. Is he?
> bye,
> Erik.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Mar 27 16:58:09 2007

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.