From owner-freebsd-stable@FreeBSD.ORG Tue May 31 18:56:13 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C419716A41C; Tue, 31 May 2005 18:56:13 +0000 (GMT) (envelope-from jd@ugcs.caltech.edu) Received: from zloty.ugcs.caltech.edu (zloty.ugcs.caltech.edu [131.215.176.114]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6963243D48; Tue, 31 May 2005 18:56:13 +0000 (GMT) (envelope-from jd@ugcs.caltech.edu) Received: by zloty.ugcs.caltech.edu (Postfix, from userid 3640) id 9869754801; Tue, 31 May 2005 11:56:12 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by zloty.ugcs.caltech.edu (Postfix) with ESMTP id 604DC49002; Tue, 31 May 2005 11:56:12 -0700 (PDT) Date: Tue, 31 May 2005 11:56:12 -0700 (PDT) From: Jon Dama To: Skylar Thompson In-Reply-To: <429C867A.5040909@cs.earlham.edu> Message-ID: References: <200505270711.j4R7BTMf078204@gw.catspoiler.org> <429C867A.5040909@cs.earlham.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Don Lewis , freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Subject: Re: Weird NFS problems X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 May 2005 18:56:13 -0000 Yes, but surely you weren't bridging gigabit and 100Mbit before? Did you try my suggestion about binding the IP address of the NFS server to the 100Mbit side? -Jon On Tue, 31 May 2005, Skylar Thompson wrote: > Jon Dama wrote: > > >Try switching to TCP NFS. > > > >a 100MBit interface cannot keep up with a 1GBit interface in a bridge > >configuration. Therefore, in the long run, at full-bore you'd expect to > >drop 9 out of every 10 ethernet frames. > > > >MTU is 1500 therefore 1K works (it fits in one frame), 2K doesn't (your > >NFS transactions are split across frames, one of which will almost > >certainly be dropped, it's UDP so the loss of one frame invalidates the > >whole transaction). > > > >This is the same reason you can't use UDP with a block size greater than > >MTU to use NFS over your DSL or some such arrangement. > > > >Incidentially, this has nothing to do with FreeBSD. So if using TCP > >mounts solves your problem, don't expect Solaris NFS to magically make the > >UDP case work... > > > > > > The thing is that UDP NFS has been working for us for years. A big part > of our work is performance analysis, so to change our network > architecture will invalidate a large part of our data. > > -- > -- Skylar Thompson (skylar@cs.earlham.edu) > -- http://www.cs.earlham.edu/~skylar/ > >