Understanding nfsstat output

[AK]

Hello everyone!

I am trying to understand the output of nfsstat to better understand and tweak NFS performance for our machines.

Following is the output from our Solaris 9, NFSv3 running server:

I am concerned about the "badcalls" for "Server nfs" output, is this normal or something is wrong. We have some of our clients mounting the exported File system with rsize & wsize = 32K, Could this be the problem, is there a way to narrow it down?

Any feedback is greatly appreciated!

~thanks ~al

# nfsstat -s

Server rpc:
Connection oriented:
calls badcalls nullrecv badlen xdrcall dupchecks
101090599 0 0 0 0 62704096
dupreqs
7038
Connectionless:
calls badcalls nullrecv badlen xdrcall dupchecks
17121084 0 0 0 0 7028935
dupreqs
69076

Server nfs:
calls badcalls
118266383 57138
Version 2: (0 calls)
null getattr setattr root lookup readlink
0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
read wrcache write create remove rename
0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
link symlink mkdir rmdir readdir statfs
0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
Version 3: (117965148 calls)
null getattr setattr lookup access readlink
1 0% 185486 0% 1906 0% 41482 0% 24091 0% 487 0%
read write create mkdir symlink mknod
47680376 40% 69594128 58% 2516 0% 2 0% 80 0% 0 0%
remove rmdir rename link readdir readdirplus
1658 0% 4 0% 126 0% 7 0% 1890 0% 2726 0%
fsstat fsinfo pathconf commit
222331 0% 9 0% 2 0% 205840 0%

Server nfs_acl:
Version 2: (0 calls)
null getacl setacl getattr access
0 0% 0 0% 0 0% 0 0% 0 0%
Version 3: (111 calls)
null getacl setacl
0 0% 73 65% 38 34%


---------------------------------
Ahhh...imagining that irresistible "new car" smell?
Check outnew cars at Yahoo! Autos.

[Peter Staubach]

Post by AK
Hello everyone!
I am trying to understand the output of nfsstat to better understand
and tweak NFS performance for our machines.
I am concerned about the "badcalls" for "Server nfs" output, is this
normal or something is wrong. We have some of our clients mounting the
exported File system with rsize & wsize = 32K, Could this be the
problem, is there a way to narrow it down?
Any feedback is greatly appreciated!
~thanks ~al
# nfsstat -s
calls badcalls nullrecv badlen xdrcall dupchecks
101090599 0 0 0 0 62704096
dupreqs
7038
calls badcalls nullrecv badlen xdrcall dupchecks
17121084 0 0 0 0 7028935
dupreqs
69076
calls badcalls
118266383 57138
Version 2: (0 calls)
null getattr setattr root lookup readlink
0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
read wrcache write create remove rename
0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
link symlink mkdir rmdir readdir statfs
0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
Version 3: (117965148 calls)
null getattr setattr lookup access readlink
1 0% 185486 0% 1906 0% 41482 0% 24091 0% 487 0%
read write create mkdir symlink mknod
47680376 40% 69594128 58% 2516 0% 2 0% 80 0% 0 0%
remove rmdir rename link readdir
readdirplus
1658 0% 4 0% 126 0% 7 0% 1890 0% 2726 0%
fsstat fsinfo pathconf commit
222331 0% 9 0% 2 0% 205840 0%
Version 2: (0 calls)
null getacl setacl getattr access
0 0% 0 0% 0 0% 0 0% 0 0%
Version 3: (111 calls)
null getacl setacl
0 0% 73 65% 38 34%
------------------------------------------------------------------------

I would suggest asking the Solaris folks for the interpretation for the
output fields in the Solaris version of nfsstat.

That said, the number appears to be a small percentage of the total
number of calls as to not worry very much about.

ps

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
NFS maillist - ***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs