Skip to contentSkip to conversation

NFS client request failure statistics?

DISCUSSION Joshua Hoblitt 3 participants 3 messages Jun 2, 2007 – Jun 4, 2007

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

Hello,

I was wondering if there is some existing means (systemtap, etc.) of getting a count of NFS client requests that have "failed" after exceeding the maximum number of retransmissions? If there is no means of getting at this information, I feel that it would be worth adding. It should be a useful stat to have in addition to the retrans count when tuning the timeo/retrans values.

I've spent a small amount of time poking around in the sources to see how difficult it would be export this information to userspace. It appears that this would be non-trivial to do as it seems that the NFS client code itself doesn't keep a count of failed requests and the procfs interface (/proc/net/rpc/nfs) is auto-generated by the sunrpc layer. Is my analysis correct?

Cheers,

-J

--

-------------------------------------------------------------------------
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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs

#1 lore raw
Quoted 5 lines · Joshua Hoblitt

Hello,

I was wondering if there is some existing means (systemtap, etc.) of getting a count of NFS client requests that have "failed" after exceeding the maximum number of retransmissions?

You can look in systemtap-0.5.13-1.fc6.rpm but I don't think there are any script that do that...

Quoted 1 line

If there is no means of getting at this information, I feel that it would be worth adding.

scripts are always welcomed! ;-)

Quoted 2 lines

It should be a useful stat to have in addition to the retrans count when tuning the timeo/retrans values.

Also take a look at the NFS/RPC metrics in /proc/self/mounts. They might have something similar to what your looking for..

Quoted 7 lines

I've spent a small amount of time poking around in the sources to see how difficult it would be export this information to userspace. It appears that this would be non-trivial to do as it seems that the NFS client code itself doesn't keep a count of failed requests and the procfs interface (/proc/net/rpc/nfs) is auto-generated by the sunrpc layer. Is my analysis correct?

Again, I would suggest you look at the /proc/self/mounts interface.

steved.

-------------------------------------------------------------------------
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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs

#2 lore raw
In reply to Joshua Hoblitt
Quoted 5 lines · Joshua Hoblitt

Hello,

I was wondering if there is some existing means (systemtap, etc.) of getting a count of NFS client requests that have "failed" after exceeding the maximum number of retransmissions?

Only "soft" mounted NFS file systems will ever "fail" a request after some number of retransmits. "hard" mounted NFS file systems will continue retrying forever. See nfs(5) for more details on using these mount options.

The Linux NFS FAQ has some wisdom about why you shouldn't use "soft" mounts, but rather "hard,intr".

Quoted 6 lines

I've spent a small amount of time poking around in the sources to see how difficult it would be export this information to userspace. It appears that this would be non-trivial to do as it seems that the NFS client code itself doesn't keep a count of failed requests and the procfs interface (/proc/net/rpc/nfs) is auto-generated by the sunrpc layer. Is my analysis correct?

The traditional statistics-keeping method is in /proc/net/rpc/nfs, but there is a new one that is exported in /proc/self/mountstats. It wouldn't be challenging to add a stat there that counted soft requests that timed out.

begin:vcard
fn:Chuck Lever
n:Lever;Chuck
org:Oracle Corporation;Corporate Architecture: Linux Projects Group adr:;;1015 Granger Avenue;Ann Arbor;MI;48104;USA title:Principal Member of Staff
tel;work:+1 248 614 5091
x-mozilla-html:FALSE
url:http://oss.oracle.com/~cel/
version:2.1
end:vcard

-------------------------------------------------------------------------
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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs