From owner-freebsd-current@FreeBSD.ORG Sun Jun 25 07:48:59 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EB27B16A4C2; Sun, 25 Jun 2006 07:48:59 +0000 (UTC) (envelope-from pcasidy@casidy.com) Received: from spock.galacsys.net (spock.galacsys.net [217.24.82.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8121143D62; Sun, 25 Jun 2006 07:48:58 +0000 (GMT) (envelope-from pcasidy@casidy.com) Received: from smtp.casidy.net (lns-bzn-51f-81-56-135-122.adsl.proxad.net [81.56.135.122]) by spock.galacsys.net (Postfix) with ESMTP id 5E940101EA; Sun, 25 Jun 2006 09:48:27 +0200 (CEST) Received: from [192.168.1.14] (unknown [192.168.1.14]) by smtp.casidy.net (Postfix) with ESMTP id 11FACB86C; Sun, 25 Jun 2006 09:55:15 +0200 (CEST) Message-ID: <449E5C2A.5000601@casidy.com> Date: Sun, 25 Jun 2006 09:49:30 +0000 From: Philippe CASIDY User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050827) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <20060620034229.GA48515@dragon.NUXI.org> In-Reply-To: <20060620034229.GA48515@dragon.NUXI.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: Often experiencing nfs server foo:/bar: not responding X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Jun 2006 07:49:00 -0000 David O'Brien wrote: > I am getting these errors all the time now (now being -CURRENT newer than > Dec'05-Jan'06 time frame). Are there some known issues in UDP or NFS > serving since then? This is on a virtually zero loaded 100Mbit network. > Both the NFS server and client are FreeBSD-CURRENT systems. > > I can trivially trigger this on all my FreeBSD-CURRENT NFS clients, > simply by exiting Vim. Did something change sometime in 2006 that would > affect the default NFS mounts? > I experience this problem from now and then too. The problem was gone when I upgraded my server to from 5.1 to 5.5-PRELEASE. Before that, I added an entry in the server's crontab to launch a script that does : #!/bin/sh /sbin/ifconfig re0 mtu 1490 /bin/sleep 15 /sbin/ifconfig re0 mtu 1500 I had then bad network performances but no more NFS lockdown. Recently, I installed a new laptop with a 6.1-STABLE (three weeks ago) and the problem reappeared. But I am not using much that laptop yet. Here is my testimony on this issue, for what it's worth ;-) Phil.