From: Chuck Lever Subject: Re: NFS client request failure statistics? Date: Mon, 04 Jun 2007 11:00:16 -0400 Message-ID: <46642900.5020502@oracle.com> References: <20070602003340.GA5482@ifa.hawaii.edu> Reply-To: chuck.lever@oracle.com Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="------------000705020004010206060205" Cc: nfs@lists.sourceforge.net To: Joshua Hoblitt Return-path: Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92] helo=mail.sourceforge.net) by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43) id 1HvE2r-0002Sw-14 for nfs@lists.sourceforge.net; Mon, 04 Jun 2007 08:00:35 -0700 Received: from agminet01.oracle.com ([141.146.126.228]) by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.44) id 1HvE2t-0004LL-Ka for nfs@lists.sourceforge.net; Mon, 04 Jun 2007 08:00:36 -0700 In-Reply-To: <20070602003340.GA5482@ifa.hawaii.edu> List-Id: "Discussion of NFS under Linux development, interoperability, and testing." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: nfs-bounces@lists.sourceforge.net Errors-To: nfs-bounces@lists.sourceforge.net This is a multi-part message in MIME format. --------------000705020004010206060205 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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. --------------000705020004010206060205 Content-Type: text/x-vcard; charset=utf-8; name="chuck.lever.vcf" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="chuck.lever.vcf" 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 --------------000705020004010206060205 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ------------------------------------------------------------------------- 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/ --------------000705020004010206060205 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs --------------000705020004010206060205--