From owner-freebsd-net@FreeBSD.ORG Wed May 11 09:06:59 2005 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 39CE516A4CE for ; Wed, 11 May 2005 09:06:59 +0000 (GMT) Received: from antsrv1.ant.uni-bremen.de (antsrv2.ant.uni-bremen.de [134.102.176.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id A54CC43D45 for ; Wed, 11 May 2005 09:06:57 +0000 (GMT) (envelope-from rebehn@ant.uni-bremen.de) Received: from bremerhaven.ant.uni-bremen.de ([134.102.176.10]) by antsrv2.ant.uni-bremen.de with esmtp (Exim 4.42) id 1DVnB8-0008Fl-0R; Wed, 11 May 2005 11:06:54 +0200 Message-ID: <4281CB3A.6080901@ant.uni-bremen.de> Date: Wed, 11 May 2005 11:07:06 +0200 From: Heinrich Rebehn User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050420 Debian/1.7.7-2 X-Accept-Language: en MIME-Version: 1.0 To: Mohan Srinivasan References: <20050510201204.57969.qmail@web80602.mail.yahoo.com> In-Reply-To: <20050510201204.57969.qmail@web80602.mail.yahoo.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Spam-Report: Spam detection software, running on the system "antsrv2.ant.uni-bremen.de", hasmessageblock similar future email. If you have any questions, see the administrator of that system for details.are very likely unrelated to the hangs. > > nfs_rephead() is called (via the contorted macros nfsm_reply() and > friends) from the NFS server routines in nfs_serv.c. The error > that was returned by the vnode op called is passed into > nfs_rephead(), whence it gets into the NFS reply. The fact that > you see these errors go up is not abnormal. In your case, over > 90% of these errors are ENOENT. > > Are you using NFS/TCP ? Can you force the mount to NFS/UDP ? [...] Content analysis details: (0.0 points, 5.0 required) pts rule name description -------------------------------------------------- cc: freebsd-net@freebsd.org Subject: Re: nfsrvstats.srvrpc_errs rapidly increasing X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 May 2005 09:06:59 -0000 Mohan Srinivasan wrote: > Hi, > > The srvrcp_errs are very likely unrelated to the hangs. > > nfs_rephead() is called (via the contorted macros nfsm_reply() and > friends) from the NFS server routines in nfs_serv.c. The error > that was returned by the vnode op called is passed into > nfs_rephead(), whence it gets into the NFS reply. The fact that > you see these errors go up is not abnormal. In your case, over > 90% of these errors are ENOENT. > > Are you using NFS/TCP ? Can you force the mount to NFS/UDP ? Yes, we use TCP. It is strongly recommended for multispeed networks and we did have problems with retransmissions using UDP. Also, in order to change to UDP for testing purposes, we would have to reboot our entire Linux cluster, which is hardly feasible. > I have seen a bug in the FreeBSD 5.x NFS server, where in the > NFS/TCP case, the stream gets out of sync. This results in the > RPC record markers to be completely wrong, confusing clients. > Now, I don't know if this bug can cause the Linux client to hang > or not, but this is definitely worth eliminating as a factor. > The FreeBSD NFS client recovers from this by tearing down the > connection and reconnecting, other clients may behave strangely. Wouldn't it be better to fix the bug? Is there a problem report on this? Some more info on my original problem: We have diskless Linux clients that mount their root fs from the FBSD server. Most times this works, but sometimes the mount simply hangs and i have to issue a "/etc/rc.d/nfsd restart" on the server. Any thoughts on this? --Heinrich