From owner-freebsd-current@FreeBSD.ORG Tue Jun 20 10:38:30 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 58A7D16A47A; Tue, 20 Jun 2006 10:38:30 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id E0E7A43D53; Tue, 20 Jun 2006 10:38:29 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 6540946B83; Tue, 20 Jun 2006 06:38:29 -0400 (EDT) Date: Tue, 20 Jun 2006 11:38:29 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Scott Long In-Reply-To: <44977E82.8040801@samsco.org> Message-ID: <20060620113745.N35462@fledge.watson.org> References: <20060620034229.GA48515@dragon.NUXI.org> <44977E82.8040801@samsco.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed 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 10:38:30 -0000 On Mon, 19 Jun 2006, Scott Long wrote: > 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. Another thing to try is to run a constant ping session in the background, and see if there are correlations between NFS errors and ping problems. It's possible the origin of the issue is actually a network driver problem. Robert N M Watson Computer Laboratory University of Cambridge