Sponsored Content
Full Discussion: nfsd
Top Forums UNIX for Advanced & Expert Users nfsd Post 302420256 by Davinzy on Tuesday 11th of May 2010 11:24:37 PM
Old 05-12-2010
nfsd

Dear Friends,

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,

Code:
Load averages: 2.40, 2.73, 2.99
711 processes: 287 sleeping, 424 running
Cpu states:
CPU   LOAD   USER   NICE    SYS   IDLE  BLOCK  SWAIT   INTR   SSYS
 0    2.74  12.1%  23.0%  62.8%   2.1%   0.0%   0.0%   0.0%   0.0%
12    2.26  25.7%  40.2%  30.0%   4.2%   0.0%   0.0%   0.0%   0.0%
13    2.09  19.4%  29.6%  45.3%   5.7%   0.0%   0.0%   0.0%   0.0%
14    2.20  13.4%  41.3%  39.1%   6.2%   0.0%   0.0%   0.0%   0.0%
15    2.30  23.4%  17.7%  52.8%   6.0%   0.0%   0.0%   0.0%   0.0%
16    2.65  16.8%  22.1%  59.4%   1.7%   0.0%   0.0%   0.0%   0.0%
24    2.53  23.4%  27.0%  47.7%   1.9%   0.0%   0.0%   0.0%   0.0%
---   ----  -----  -----  -----  -----  -----  -----  -----  -----
avg   2.40  19.2%  28.6%  48.2%   4.0%   0.0%   0.0%   0.0%   0.0%

System Page Size: 4Kbytes
Memory: 19777212K (15964960K) real, 29382676K (21944844K) virtual, 6644196K free  Page# 1/28

CPU TTY    PID USERNAME PRI NI   SIZE    RES STATE    TIME %WCPU  %CPU COMMAND
16   ?    2607 root     152 20 62400K 15372K run   4030:43 78.14 78.01 nfsd
13   ?   20489 cgi      152 20  3476M  3449M run    535:59 72.39 72.26 uu_ccc_sss
14   ?   22075 cgi      152 30 52400K 24696K run      0:13 48.37 36.44 xx_yyy_mmm

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...
 

6 More Discussions You Might Find Interesting

1. Solaris

nfsd won't start at boot up

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)
Discussion started by: dcshungu
19 Replies

2. UNIX for Dummies Questions & Answers

don't have nfsd mount point in /proc/fs/nfsd

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)
Discussion started by: alirezan
1 Replies

3. AIX

portmap and nfsd

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)
Discussion started by: pitmod
3 Replies

4. BSD

NFSD under OpenBSD

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)
Discussion started by: smoofy
1 Replies

5. HP-UX

NFSd command utilizing more cpu

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)
Discussion started by: Maddy123
4 Replies

6. Slackware

NFSd problem

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
prstat(1M)                                                                                                                              prstat(1M)

NAME
prstat - report active process statistics SYNOPSIS
prstat [-acJLmRtTv] [-C psrsetlist] [-j projlist] [-k tasklist] [-n ntop[,nbottom]] [-p pidlist] [-P cpulist] [-s key | -S key ] [-u euidlist] [-U uidlist] [-z zoneidlist] [-Z] [interval [count]] The prstat utility iteratively examines all active processes on the system and reports statistics based on the selected output mode and sort order. prstat provides options to examine only processes matching specified PIDs, UIDs, zone IDs, CPU IDs, and processor set IDs. The -j, -k, -C, -p, -P, -u, -U, and -z options accept lists as arguments. Items in a list can be either separated by commas or enclosed in quotes and separated by commas or spaces. If you do not specify an option, prstat examines all processes and reports statistics sorted by CPU usage. The following options are supported: -a Report information about processes and users. In this mode prstat displays separate reports about processes and users at the same time. -c Print new reports below previous reports instead of overprinting them. -C psrsetlist Report only processes or lwps that are bound to processor sets in the given list. Each processor set is identified by an integer as reported by psrset(1M). The load averages displayed are the sum of the load averages of the specified processor sets (see pset_getload- avg(3C)). Processes with one or more LWPs bound to processor sets in the given list are reported even when the -L option is not used. -j projlist Report only processes or lwps whose project ID is in the given list. Each project ID can be specified as either a project name or a numerical project ID. See project(4). -J Report information about processes and projects. In this mode prstat displays separate reports about processes and projects at the same time. -k tasklist Report only processes or lwps whose task ID is in tasklist. -L Report statistics for each light-weight process (LWP). By default, prstat reports only the number of LWPs for each process. -m Report microstate process accounting information. In addition to all fields listed in -v mode, this mode also includes the percentage of time the process has spent processing system traps, text page faults, data page faults, waiting for user locks and waiting for CPU (latency time). -n ntop[,nbottom] Restrict number of output lines. The ntop argument determines how many lines of process or lwp statistics are reported, and the nbottom argument determines how many lines of user, task, or projects statistics are reported if the -a, -t, -T, or -J options are specified. By default, prstat displays as many lines of output that fit in a window or terminal. When you specify the -c option or direct the out- put to a file, the default values for ntop and nbottom are 15 and 5. -p pidlist Report only processes whose process ID is in the given list. -P cpulist Report only processes or lwps which have most recently executed on a CPU in the given list. Each CPU is identified by an integer as reported by psrinfo(1M). -R Put prstat in the real time scheduling class. When this option is used, prstat is given priority over time-sharing and interactive pro- cesses. This option is available only for superuser. -s key Sort output lines (that is, processes, lwps, or users) by key in descending order. Only one key can be used as an argument. There are five possible key values: cpu Sort by process CPU usage. This is the default. pri Sort by process priority. rss Sort by resident set size. size Sort by size of process image. time Sort by process execution time. -S key Sort output lines by key in ascending order. Possible key values are the same as for the -s option. See -s. -t Report total usage summary for each user. The summary includes the total number of processes or LWPs owned by the user, total size of process images, total resident set size, total cpu time, and percentages of recent cpu time and system memory. -T Report information about processes and tasks. In this mode prstat displays separate reports about processes and tasks at the same time. -u euidlist Report only processes whose effective user ID is in the given list. Each user ID may be specified as either a login name or a numerical user ID. -U uidlist Report only processes whose real user ID is in the given list. Each user ID may be specified as either a login name or a numerical user ID. -v Report verbose process usage. This output format includes the percentage of time the process has spent in user mode, in system mode, and sleeping. It also includes the number of voluntary and involuntary context switches, system calls and the number of signals received. Statistics that are not reported are marked with the - sign. -z zoneidlist Report only processes or LWPs whose zone ID is in the given list. Each zone ID can be specified as either a zone name or a numerical zone ID. See zones(5). -Z Report information about processes and zones. In this mode, prstat displays separate reports about processes and zones at the same time. OUTPUT
The following list defines the column headings and the meanings of a prstat report: PID The process ID of the process. USERNAME The real user (login) name or real user ID. SIZE The total virtual memory size of the process, including all mapped files and devices, in kilobytes (K), megabytes (M), or gigabytes (G). RSS The resident set size of the process (RSS), in kilobytes (K), megabytes (M), or gigabytes (G). The RSS value is an estimate provided by proc(4) that might underestimate the actual resident set size. Users who want to get more accurate usage information for capacity plan- ning should use the -x option to pmap(1) instead. STATE The state of the process: cpuN Process is running on CPU N. sleep Sleeping: process is waiting for an event to complete. run Runnable: process in on run queue. zombie Zombie state: process terminated and parent not waiting. stop Process is stopped. PRI The priority of the process. Larger numbers mean higher priority. NICE Nice value used in priority computation. Only processes in certain scheduling classes have a nice value. TIME The cumulative execution time for the process. CPU The percentage of recent CPU time used by the process. If executing in a non-global zone and the pools facility is active, the percent- age will be that of the processors in the processor set in use by the pool to which the zone is bound. PROCESS The name of the process (name of executed file). LWPID The lwp ID of the lwp being reported. NLWP The number of lwps in the process. With the some options, in addition to a number of the column headings shown above, there are: NPROC Number of processes in a specified collection. MEMORY Percentage of memory used by a specified collection of processes. The following columns are displayed when the -v or -m option is specified USR The percentage of time the process has spent in user mode. SYS The percentage of time the process has spent in system mode. TRP The percentage of time the process has spent in processing system traps. TFL The percentage of time the process has spent processing text page faults. DFL The percentage of time the process has spent processing data page faults. LCK The percentage of time the process has spent waiting for user locks. SLP The percentage of time the process has spent sleeping. LAT The percentage of time the process has spent waiting for CPU. VCX The number of voluntary context switches. ICX The number of involuntary context switches. SCL The number of system calls. SIG The number of signals received. Under the -L option, one line is printed for each lwp in the process and some reporting fields show the values for the lwp, not the process. OPERANDS
The following operands are supported: count Specifies the number of times that the statistics are repeated. By default, prstat reports statistics until a termination signal is received. interval Specifies the sampling interval in seconds; the default interval is 5 seconds. Example 1: Reporting the Five Most Active Super-User Processes The following command reports the five most active super-user processes running on CPU1 and CPU2: example% prstat -u root -n 5 -P 1,2 1 1 PID USERNAME SIZE RSS STATE PRI NICE TIME CPU PROCESS/LWP 306 root 3024K 1448K sleep 58 0 0:00.00 0.3% sendmail/1 102 root 1600K 592K sleep 59 0 0:00.00 0.1% in.rdisc/1 250 root 1000K 552K sleep 58 0 0:00.00 0.0% utmpd/1 288 root 1720K 1032K sleep 58 0 0:00.00 0.0% sac/1 1 root 744K 168K sleep 58 0 0:00.00 0.0% init/1 TOTAL: 25, load averages: 0.05, 0.08, 0.12 Example 2: Displaying Verbose Process Usage Information The following command displays verbose process usage information about processes with lowest resident set sizes owned by users root and john. example% prstat -S rss -n 5 -vc -u root,john PID USERNAME USR SYS TRP TFL DFL LCK SLP LAT VCX ICX SCL SIG PROCESS/LWP 1 root 0.0 0.0 - - - - 100 - 0 0 0 0 init/1 102 root 0.0 0.0 - - - - 100 - 0 0 3 0 in.rdisc/1 250 root 0.0 0.0 - - - - 100 - 0 0 0 0 utmpd/1 1185 john 0.0 0.0 - - - - 100 - 0 0 0 0 csh/1 240 root 0.0 0.0 - - - - 100 - 0 0 0 0 powerd/4 TOTAL: 71, load averages: 0.02, 0.04, 0.08 The following exit values are returned: 0 Successful completion. 1 An error occurred. See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ |ATTRIBUTE TYPE |ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ proc(1), psrinfo(1M), psrset(1M), sar(1M), pset_getloadavg(3C), proc(4), project(4), attributes(5), zones(5) The snapshot of system usage displayed by prstat is true only for a split-second, and it may not be accurate by the time it is displayed. When the -m option is specified, prstat tries to turn on microstate accounting for each process; the original state is restored when prstat exits. See proc(4) for additional information about the microstate accounting facility. The total memory size reported in the SIZE and RSS columns for groups of processes can sometimes overestimate the actual amount of memory used by processes with shared memory segments. 13 Sep 2005 prstat(1M)
All times are GMT -4. The time now is 01:54 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy