I have two 9.2 machines sharing filesystems through NFS. I'm getting really poor read/write performance on the client machine (less than 1MB/sec on a gigabit LAN). Not a connectivity problem; I can copy files at high transfer rates using ssh or ftp, and nic card has 0 packet loss.
I'm pretty sure the problem is with statd on the client machine. rpcinfo -p on the client shows portmapper, nlockmgr, ypbind, nfs, and mountd running. rpcinfo -p on the server shows all those plus ypserv, fypxfrd, yppasswd, nfs_acl, and status (100024).
NFS HOWTO says that one should run statd via /sbin/rpc.statd, but that program is not present on either client or server.
The error messages the client reports are either "nfs: server xxx not responding" or "lockd: failed to monitor x.x.x.x"
I read mention of a kernel-implemented statd, but no information on how to enable/disable such a beast.
Questions:
1) Does Suse 9.2 use kernel NFS and/or kernel statd?
2) Does this sound like a statd problem?
3) How do I enable statd on 9.2? |