we are using HP-UX B.11.31 U ia64 HP-UX server. Can you check bellow the top command output whether can point out any abnormality. Becoz i suspect something wrong there,
thanks !
---------- Post updated 05-12-10 at 08:54 AM ---------- Previous update was 05-11-10 at 03:47 PM ----------
sorry guys if above content is not clear.
Actually what I want to know is what is the nfsd process running under root. I guess it is something related to OS nfs processors.
But should it take so much of the processor resource , and why the nice is getting 28% of CPU.
Is these normal .... ?
Last edited by pludi; 05-11-2010 at 07:37 AM..
Reason: code tags, please...
Hi
Inexplicably, nfsd no longer starts automatically on our Sun boxes running Solaris 9, so that 'automount' no longer functions automatically. The problem first manifested itself when we could not access files on any of the nfs automounted directories in our LAN after one of the servers (say... (19 Replies)
hi guys
I installed NFS server and everything started out fine but I don't have /proc/fs/nfsd entry and so I can't mount nfsd. Therefore I can't start my nfs service.
Why don't I have /proc/fs/nfsd? How do I create that?
Thanks (1 Reply)
Hello,
what is the relation between portmap and nfsd and how communication between them looks like. Does the nfsclient contact with the portmap or nfsd first.
Many thanks in advance for helping me to understand this :)
BR,
p (3 Replies)
Hi all,
I am having a following problem. Trying to run PXE boot server on my OpenBSD machine I have ended up on making NFSd daemon works. On all machines I get an error msg. nfsd : nfsd count is invalid: (null) no matter what computer I run it on. Everything works just well on FreeBSD and linux.... (1 Reply)
Hi,
I see following 'nfsd' command is using more CPU. Could someone please comment on it's pros and cons of it?
CPU TTY PID USERNAME PRI NI SIZE RES STATE TIME %WCPU %CPU COMMAND
5 ? 16890 root 152 20 34696K 12036K run 57166:48 856.13 854.64 nfsd
OS -- HP-UX
One... (4 Replies)
Hi.
Using debian 8.0 on a raspberryPI SERVER, accessing nfs from another raspberry gives quick reply.
But from a slackware 14.1 SERVER on a Celeron 2Ghz dual core, is painfully slow and i cannot figure out why.
Can anyone guide me? (2 Replies)
Discussion started by: dimples
2 Replies
LEARN ABOUT SUSE
rpc.nfsd
rpc.nfsd(8) System Manager's Manual rpc.nfsd(8)NAME
rpc.nfsd - NFS server process
SYNOPSIS
/usr/sbin/rpc.nfsd [options] nproc
DESCRIPTION
The rpc.nfsd program implements the user level part of the NFS service. The main functionality is handled by the nfsd kernel module. The
user space program merely specifies what sort of sockets the kernel service should listen on, what NFS versions it should support, and how
many kernel threads it should use.
The rpc.mountd server provides an ancillary service needed to satisfy mount requests by NFS clients.
OPTIONS -d or --debug
enable logging of debugging messages
-H or --host hostname
specify a particular hostname (or address) that NFS requests will be accepted on. By default, rpc.nfsd will accept NFS requests on
all known network addresses. Note that lockd (which performs file locking services for NFS) may still accept request on all known
network addresses. This may change in future releases of the Linux Kernel.
-p or --port port
specify a diferent port to listen on for NFS requests. By default, rpc.nfsd will listen on port 2049.
-N or --no-nfs-version vers
This option can be used to request that rpc.nfsd does not offer certain versions of NFS. The current version of rpc.nfsd can support
both NFS version 2,3 and the newer version 4.
-s or --syslog
By default, rpc.nfsd logs error messages (and debug messages, if enabled) to stderr. This option makes rpc.nfsd log these messages
to syslog instead. Note that errors encountered during option processing will still be logged to stderr regardless of this option.
-T or --no-tcp
Disable rpc.nfsd from accepting TCP connections from clients.
-U or --no-udp
Disable rpc.nfsd from accepting UDP connections from clients.
nproc specify the number of NFS server threads. By default, just one thread is started. However, for optimum performance several threads
should be used. The actual figure depends on the number of and the work load created by the NFS clients, but a useful starting point
is 8 threads. Effects of modifying that number can be checked using the nfsstat(8) program.
Note that if the NFS server is already running, then the options for specifying host, port, and protocol will be ignored. The number of
processes given will be the only option considered, and the number of active nfsd processes will be increased or decreased to match this
number. In particular rpc.nfsd 0 will stop all threads and thus close any open connections.
NOTES
If the program is built with TI-RPC support, it will enable any protocol and address family combinations that are marked visible in the
netconfig database.
SEE ALSO rpc.mountd(8), exports(5), exportfs(8), rpc.rquotad(8), nfsstat(8), netconfig(5).
AUTHOR
Olaf Kirch, Bill Hawes, H. J. Lu, G. Allan Morris III, and a host of others.
7 Aug 2006 rpc.nfsd(8)