From owner-freebsd-current@FreeBSD.ORG Tue Jun 20 04:50:24 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 EF37216A47E; Tue, 20 Jun 2006 04:50:24 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 65B3343D46; Tue, 20 Jun 2006 04:50:16 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k5K4oA91095014; Mon, 19 Jun 2006 22:50:15 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <44977E82.8040801@samsco.org> Date: Mon, 19 Jun 2006 22:50:10 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416 X-Accept-Language: en-us, en MIME-Version: 1.0 To: obrien@freebsd.org References: <20060620034229.GA48515@dragon.NUXI.org> In-Reply-To: <20060620034229.GA48515@dragon.NUXI.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org Cc: freebsd-current@freebsd.org 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: Tue, 20 Jun 2006 04:50:25 -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? > A number of NFS changes happened in the first quarter of 2006, but they were all focused on fixing existing bugs. I've done extensive NFS client testing with 6.1 and haven't seen anything unusual like you report, but I definitely wouldn't rule out the possibility for accidental problems. The best way to start debugging this is to capture the packet stream with tcpdump; I always run it in raw capture mode and then use other tools to analyze the output. Scott