Messages in this thread | | | Date | Wed, 7 Apr 1999 14:40:59 +0200 (CEST) | Subject | Re: Scary NFS messages.... | From | Trond Myklebust <> |
| |
>>>>> " " == Wai-Sun Chia <waisun.chia@digital.com> writes:
> Trond Myklebust wrote: >> >> Wai-Sun Chia <waisun.chia@msa.dec.com> writes: >> >> > Portmapper, rpc is working, nis is working.... >> > >> > Any ideas anybody? >> > >> > Apr 7 16:18:25 host kernel: lockd: failed to monitor >> > 192.168.34.20 Apr 7 16:28:00 host kernel: nsm_mon_unmon: rpc >> > failed, status=-43 Apr 7 16:28:00 host kernel: lockd: failed >> > to monitor 192.168.34.20 >> >> This is a FAQ. Please run the 'statd' daemon from the knfsd >> package...>
> Sorry, but which FAQ? URL please? Dejanews search shows that ^^^^^^^^^^^^^^^ That's what I meant. It is a frequently asked question...
> this is quite a common problem, and some of the answers > suggests upgrading nfsd to beta40 (does that help?)...
The messages are occurring because your NFS client is trying to use the 'rpc.lockd' protocol for file locking. Upgrading your server will not help get rid of these messages. Rather, you need to run an 'rpc.statd' daemon on the client (and on the host) in order to monitor the locks if you want to use NFS file locking. Linux does not support locking using unmonitored locks.
If not, you should rather be mounting the partitions with NFS file locking disabled. On linux clients, this is done using the 'nolock' mount option: mount -t nfs -onolock my:/foo /bar
NB: The Linux userland NFS server does not support file locking, so you always want to use the 'nolock' option when mounting from such a host (and you won't need the 'statd' daemon. Only the knfsd server currently supports file locking under Linux.
Cheers, Trond
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |