I've also found that having the server that is serving also act as a client
(even by mounting something from localhost) can make the problem go away.
Rumour has it Adam Shand, on or about 06/02/2005 11:37 PM, whispered:
> As a follow up for Google (and anyone else that's interested) ...
>
> I had this symptom as well and the problem was simply that statd had died.
>
> Simply restarting statd (or in my case "/etc/init.d/nfs-common
> restart") solved the problem.
>
> Adam.
>
>
>
>> Hi Greg,
>>
>> Since this will quickly degenerate into an NFS mail perhaps it should
>> be off list? Then again, other might encounter the same
>> problem so I just put an [OT] warning in.
>>
>> The NFS server is running Slackware 10 (their latest June release)
>> with a 2.6.7 kernel. It is compiled with all the NFS options
>> turned on:
>>
>> # Network File Systems
>> #
>> CONFIG_NFS_FS=y
>> CONFIG_NFS_V3=y
>> CONFIG_NFS_V4=y
>> CONFIG_NFS_DIRECTIO=y
>> CONFIG_NFSD=y
>> CONFIG_NFSD_V3=y
>> CONFIG_NFSD_V4=y
>> CONFIG_NFSD_TCP=y
>> CONFIG_LOCKD=y
>> CONFIG_LOCKD_V4=y
>> CONFIG_EXPORTFS=y
>> CONFIG_SUNRPC=y
>> CONFIG_SUNRPC_GSS=y
>> CONFIG_RPCSEC_GSS_KRB5=y
>> CONFIG_SMB_FS=y
>> CONFIG_SMB_NLS_DEFAULT=y
>> CONFIG_SMB_NLS_REMOTE="cp437"
>> CONFIG_CIFS=y
>> CONFIG_CIFS_STATS=y
>>
>> And it is exported using the command:
>> /mnt/hd/ 192.168.0.0/255.255.0.0(sync,rw,no_root_squash)
>>
>> The native file system is XFS.
>>
>> My client is another Slackware 10 + kernel 2.6.7 system compiled with
>> #
>> # Network File Systems
>> #
>> CONFIG_NFS_FS=y
>> CONFIG_NFS_V3=y
>> # CONFIG_NFS_V4 is not set
>> # CONFIG_NFS_DIRECTIO is not set
>> CONFIG_NFSD=y
>> CONFIG_NFSD_V3=y
>> # CONFIG_NFSD_V4 is not set
>> # CONFIG_NFSD_TCP is not set
>> # CONFIG_ROOT_NFS is not set
>> CONFIG_LOCKD=y
>> CONFIG_LOCKD_V4=y
>> CONFIG_EXPORTFS=y
>> CONFIG_SUNRPC=y
>> # CONFIG_RPCSEC_GSS_KRB5 is not set
>> CONFIG_SMB_FS=y
>>
>> And as I said, mounted with
>> 192.168.101.12:/mnt/hd/home/svn /data/svn-nfs-repos nfs
>>
>> user,nfsvers=3,rsize=8192,timeo=14,tcp,hard,lock,intr,wsize=8192,noauto
>> ,posix 0 0
>>
>> Do you have any suggestions? I assume I am doing something obviously
>> wrong but I am new to this whole NFS thing.
>>
>> Thanks,
>> Chris
>>
>> It is whispered that Greg Hudson was heard, on or about 08/18/04
>> 00:30 to say:
>> >>svnadmin load /data/svn-nfs-repos/go-dev < go-dev.dmp
>> >>svn: Error opening db lockfile
>> >>svn: Can't get shared lock on file
>> '/data/svn-nfs-repos/go-dev/locks/db.lock': No locks available
>> >
>> >
>> > Although FSFS is designed to be less picky than BDB about the
>> > underlying file store, it does require the ability to perform file
>> > locking. That might change in the future, but for now it's a
>> > requirement.
>> >
>> > You didn't give much information about your NFS server platform (or
>> > the client platform); if your server is the old user-space Linux NFS
>> > server, I believe upgrading to the newer kernel nfsd might help.
>> >
>>
>> --
>> Chris Beck / Y.A.B.A. / Fungal Genomics / Concordia University / tel.
>> ext. 5791
>> "We do not inherit the Earth from our Ancestors,
>> we borrow it from our Children."
>
>
>
--
Chris Beck - http://pacanukeha.blogspot.com
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
-Benjamin Franklin, Historical Review of Pennsylvania, 1753
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Feb 7 20:56:56 2005