All of lore.kernel.org
 help / color / mirror / Atom feed
* Understanding nfsstat output
@ 2007-05-02 15:26 AK
  2007-05-02 20:30 ` Peter Staubach
  0 siblings, 1 reply; 2+ messages in thread
From: AK @ 2007-05-02 15:26 UTC (permalink / raw)
  To: nfs


[-- Attachment #1.1: Type: text/plain, Size: 2426 bytes --]

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.

[-- Attachment #1.2: Type: text/html, Size: 6203 bytes --]

[-- Attachment #2: Type: text/plain, Size: 286 bytes --]

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

[-- Attachment #3: Type: text/plain, Size: 140 bytes --]

_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Understanding nfsstat output
  2007-05-02 15:26 Understanding nfsstat output AK
@ 2007-05-02 20:30 ` Peter Staubach
  0 siblings, 0 replies; 2+ messages in thread
From: Peter Staubach @ 2007-05-02 20:30 UTC (permalink / raw)
  To: AK; +Cc: nfs

AK wrote:
> 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%
>
> ------------------------------------------------------------------------

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  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2007-05-02 20:30 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-05-02 15:26 Understanding nfsstat output AK
2007-05-02 20:30 ` Peter Staubach

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.