From owner-freebsd-current@FreeBSD.ORG Tue Jun 20 20:26:58 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 EC76D16A479; Tue, 20 Jun 2006 20:26:58 +0000 (UTC) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9023A43D6B; Tue, 20 Jun 2006 20:26:58 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (obrien@localhost [127.0.0.1]) by dragon.NUXI.org (8.13.6/8.13.6) with ESMTP id k5KKQwQr045915; Tue, 20 Jun 2006 13:26:58 -0700 (PDT) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.6/8.13.1/Submit) id k5KKQwGw045914; Tue, 20 Jun 2006 13:26:58 -0700 (PDT) (envelope-from obrien) Date: Tue, 20 Jun 2006 13:26:54 -0700 From: "David O'Brien" To: Robert Watson Message-ID: <20060620202654.GB45624@dragon.NUXI.org> Mail-Followup-To: obrien@freebsd.org, Robert Watson , freebsd-current@freebsd.org References: <20060620034229.GA48515@dragon.NUXI.org> <44977E82.8040801@samsco.org> <20060620113745.N35462@fledge.watson.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060620113745.N35462@fledge.watson.org> X-Operating-System: FreeBSD 7.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 User-Agent: Mutt/1.5.11 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 Reply-To: obrien@FreeBSD.org 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 20:26:59 -0000 On Tue, Jun 20, 2006 at 11:38:29AM +0100, Robert Watson wrote: > It's possible the origin of the issue is actually a network driver problem. I experience this with a wide range of NICs for the client (nve, bge, gem), and both bge(4) and sk(4) for the server. -- -- David (obrien@FreeBSD.org) Q: Because it reverses the logical flow of conversation. A: Why is top-posting (putting a reply at the top of the message) frowned upon?