From: Trond Myklebust Subject: Re: Trying to determine why my NFS connection goes away Date: Sat, 16 Jun 2007 00:03:49 -0400 Message-ID: <1181966629.6135.27.camel@heimdal.trondhjem.org> References: <1181874951.15174.15.camel@heimdal.trondhjem.org> <1181915360.6135.7.camel@heimdal.trondhjem.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Cc: nfs@lists.sourceforge.net To: mike Return-path: Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91] helo=mail.sourceforge.net) by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43) id 1HzPVy-0000AS-ER for nfs@lists.sourceforge.net; Fri, 15 Jun 2007 21:03:56 -0700 Received: from pat.uio.no ([129.240.10.15] ident=[U2FsdGVkX18rEtPdlPb0X8Kqjo4YuzlJcGTlODnWfYU=]) by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.44) id 1HzPW1-00086U-5o for nfs@lists.sourceforge.net; Fri, 15 Jun 2007 21:03:57 -0700 In-Reply-To: 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 On Fri, 2007-06-15 at 15:32 -0700, mike wrote: > On 6/15/07, Trond Myklebust wrote: > > Then why on earth are you using timeo=10? Use the default timeo=600 and > > it will all work. > > > > Using overly short timeouts on TCP is completely unnecessary: TCP > > provides reliable delivery of data. Furthermore, a timeout forces the > > client to keep disconnecting and reconnecting, and that is why you are > > seeing those messages. > > I think that was one of the suggestions (I've Googled a lot, tried > different things, etc.) when looking at tuning NFS and such. > > I have now mounted it as such: > > raid01:/home on /local/home type nfs > (rw,nodev,_netdev,noatime,nfsvers=3,tcp,rsize=16384,wsize=16384,hard,intr,nolock,timeo=600,addr=192.168.1.151) > > I still consistently and easily get the > > [root@web03 ~]# dmesg -c > nfs: server raid01 not responding, still trying > nfs: server raid01 OK > nfs: server raid01 not responding, still trying > nfs: server raid01 OK > > After only a minute or two of nhfsstone (with default parameters) > > Any other suggestions? Increasing/decreasing wsize/rsize? Changing > hard to soft? I'm willing to try anything. Did you check that the above parameters are indeed set in /proc/mounts? Trond ------------------------------------------------------------------------- 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