Celso Tadao Suzuki <celso.suz...@digitro.com.br> writes:
> *The NFS server is a Linux box with Red Hat 5. Kernel **2.6.18-53.1.4.el5PAE**
> **
> **I mount with these options */*exec,dev,suid,rw,noauto*/
> stat64("/home2/celso/SVN/tcf/.svn/tmp/wcng/.svn/wc.db", 0xbfa22a58) = -1
> ENOENT (No such file or directory)
> open("/home2/celso/SVN/tcf/.svn/tmp/wcng/.svn/wc.db",
> O_RDWR|O_CREAT|O_LARGEFILE|O_CLOEXEC, 0644) = 3
> fstat64(3, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
> _llseek(3, 0, [0], SEEK_SET) = 0
> read(3, "", 100) = 0
> fcntl64(3, F_SETLK64, {type=F_RDLCK, whence=SEEK_SET, start=1073741824,
> len=1}, 0xbfa22ac8) = -1 ENOLCK (No locks available)
> nanosleep({0, 1000000}, NULL) = 0
> fcntl64(3, F_SETLK64, {type=F_RDLCK, whence=SEEK_SET, start=1073741824,
> len=1}, 0xbfa22ac8) = -1 ENOLCK (No locks available)
That's an NFS problem, the man page for fcntl says:
ENOLCK Too many segment locks open, lock table is full, or a remote locking
protocol failed (e.g., locking over NFS).
Perhaps you don't have the NFS locking daemon running?
--
Certified & Supported Apache Subversion Downloads:
http://www.wandisco.com/subversion/download
