From owner-freebsd-stable@FreeBSD.ORG Sat May 28 12:46:05 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 BFE1816A41C; Sat, 28 May 2005 12:46:05 +0000 (GMT) (envelope-from owner-freebsd-questions@freebsd.org) Received: from rutherford.zen.co.uk (rutherford.zen.co.uk [212.23.3.142]) by mx1.FreeBSD.org (Postfix) with ESMTP id 88F0F43D54; Sat, 28 May 2005 12:46:03 +0000 (GMT) (envelope-from owner-freebsd-questions@freebsd.org) Received: from [82.69.255.54] (helo=rtxnetworks.co.uk) by rutherford.zen.co.uk with esmtp (Exim 4.34) id 1Dc0hW-0003pI-HD; Sat, 28 May 2005 12:46:02 +0000 Received: from mail pickup service by rtxnetworks.co.uk with Microsoft SMTPSVC; Sat, 28 May 2005 13:45:45 +0100 thread-index: AcVjgyoBSFh0IBNhSzeBHKMdqiMVgQ== X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Date: Sat, 28 May 2005 13:45:44 +0100 From: "Jon Dama" To: Message-ID: <001301c56383$2a042ef0$144da8c0@rtxnetworks.local> In-Reply-To: <200505270711.j4R7BTMf078204@gw.catspoiler.org> Content-Transfer-Encoding: 7bit References: <200505270711.j4R7BTMf078204@gw.catspoiler.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset="US-ASCII" X-Mailer: Microsoft CDO for Exchange 2000 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Sender: Errors-To: owner-freebsd-questions@freebsd.org X-Zen-Test-Spam-Score: 0 X-Zen-Test-Spam-Bar: (/) X-Originating-Schroedinger-IP: [216.136.204.119] Content-Class: urn:content-classes:message X-Envelope-From: owner-freebsd-questions@freebsd.org Importance: normal Priority: normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.181 X-Envelope-To: james@rtxnetworks.co.uk X-Apparently-To: james@rtxnetworks.co.uk X-Zen-Loop: 4e5e9d7b303bfa0036200918db506edf X-Zen-Stored: hausdorff.zen.co.uk/1Dc0fg-00027L-Fr/2005-05-28 12:44:08 X-Antivirus: AVG for E-mail 7.0.322 [267.2.0] X-OriginalArrivalTime: 28 May 2005 12:45:45.0031 (UTC) FILETIME=[2A3B1D70:01C56383] X-Originating-Rutherford-IP: [82.69.255.54] Cc: freebsd-stable@freebsd.org, skylar@cs.earlham.edu, freebsd-questions@freebsd.org Subject: Re: Weird NFS problems X-BeenThere: freebsd-stable@freebsd.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 May 2005 12:46:06 -0000 Oh, something else to try: I checked through my notes and discovered that I had gotten UDP to work in a similar configuration before. What I did was bind the IP address to fxp0 instead of em0. By doing this, the kernel seems to send the data at a pace suitable for the slow interface. -Jon On Fri, 27 May 2005, Don Lewis wrote: > On 26 May, Skylar Thompson wrote: > > I'm having some problems with NFS serving on a FreeBSD 5.4-RELEASE > > machine. The FreeBSD machine is the NFS/NIS server for a group of four > > Linux clusters. The network archictecture looks like this: > > > > 234/24 234/24 > > Cluster 1 --- |--------------- Cluster 3 > > | --------------- > > em0| File server | fxp0 > > | -------------- > > Cluster 2 --- |--------------- Cluster 4 > > 234/24 230/24 > > > > > > em0 and fxp0 are bridged, and em0 has a 234/24 IP address while fxp0 is > > just in promiscuous mode. 234/24 is an 802.1q VLAN on the fxp0 side of > > the server, so packets are untagged at the switch just before fxp0, and > > are forwarded to em0 through the bridge. > > > > The problem manifests itself in large UDP NFS requests from Clusters 3 > > and 4. The export can be mounted fine from both those clusters, and > > small transfers such as with ls work fine, but the moment any serious > > data transfer starts, the entire mount just hangs. Running ethereal on > > the file server shows a a lot of fragmented packets, and RPC > > retransmissions on just a single request. Reducing the read and write > > NFS buffers on the Linux clients to 1kB from the default of 4kB solves > > the issue, but kills the transfer rate. The moment I go to 2kB, the > > problem reappearss. Clusters 1 and 2 use the default of 4kB buffers, and > > have no problems communicating to em0. > > > > Poking through the list archives, I ran across this message > > (http://lists.freebsd.org/pipermail/freebsd-stable/2003-May/001007.html) > > that reveals a bug in the fxp(4) driver in 4-RELEASE that incorrectly > > detects the capabilities of the NIC. Is this still an issue in > > 5-RELEASE, or am I looking at a different problem? Any ideas on how I > > can get the NFS buffers up to a reasonable level? > > That problem was fixed quite some time ago. > > Which transfer direction fails? > Client writing to server > Client reading from server > Both? > > Do you see all the fragments in the retransmitted request? > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"