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

Re: working copy on NFS

From: Andreas Schmid <anschmid_at_ira.uka.de>
Date: 2005-12-13 15:32:03 CET

> On Wed, 2005-11-23 at 17:13 +0100, Vincent Lefevre wrote:
>
>>On 2005-11-23 15:30:19 +0100, Daniel Drotos wrote:
>>
>>>The book mentions that the repository should be created on a local
>>>filesystem.
>>
>>Is it also true for FSFS?
>>
>>
>>>What about the working copy?
>>
>>No problem, except for the well-known problems of NFS.
>>
>
>
>
> Actually, we explicitly say it work in the FAQ:
> "
> Working copies can be stored on NFS (one common scenario is when your
> home directory is on a NFS server). On Linux NFS servers, due to the
> volume of renames used internally in Subversion when checking out files,
> some users have reported that 'subtree checking' should be disabled
> (it's enabled by default). Please see NFS Howto Server Guide and
> exports(5) for more information on how to disable subtree checking.
> "
>
> And on IRC, it has been used as a reason why we do locking the way we
> do.
> So if it doesn't actually work to store a working copy on NFS, we
> should either
>
> 1. Fix it
>
> or
>
> 2. Use real locks, and stop claiming storing working copy works on NFS
> on nfs implementations where locking doesn't work.
>
> (I actually think #2 is the better solution, because i think that we
> shouldn't work around everybody elses bugs, particularly when it causes
> large performance loss for us)
>

It doesn't work for me either, a checkout fails with the comment:

svn: Stale NFS file handle
svn: svn_io_set_file_read_only: failed to set file 'doc/.svn/entries'
read-only

Andreas

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Dec 13 21:18:53 2005

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