From: Chuck Lever <chuck.lever@oracle.com>
To: Joshua Hoblitt <jhoblitt@ifa.hawaii.edu>
Cc: nfs@lists.sourceforge.net
Subject: Re: NFS client request failure statistics?
Date: Mon, 04 Jun 2007 11:00:16 -0400 [thread overview]
Message-ID: <46642900.5020502@oracle.com> (raw)
In-Reply-To: <20070602003340.GA5482@ifa.hawaii.edu>
[-- Attachment #1: Type: text/plain, Size: 1168 bytes --]
Joshua Hoblitt wrote:
> 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".
> 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.
[-- Attachment #2: chuck.lever.vcf --]
[-- Type: text/x-vcard, Size: 291 bytes --]
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
[-- Attachment #3: 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 #4: Type: text/plain, Size: 140 bytes --]
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2007-06-04 15:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-02 0:33 NFS client request failure statistics? Joshua Hoblitt
2007-06-02 10:21 ` Steve Dickson
2007-06-04 15:00 ` Chuck Lever [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46642900.5020502@oracle.com \
--to=chuck.lever@oracle.com \
--cc=jhoblitt@ifa.hawaii.edu \
--cc=nfs@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.