From owner-freebsd-stable@FreeBSD.ORG Fri May 27 07:16:26 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 9E32B16A41C; Fri, 27 May 2005 07:16:26 +0000 (GMT) (envelope-from owner-freebsd-questions@freebsd.org) Received: from heisenberg.zen.co.uk (heisenberg.zen.co.uk [212.23.3.141]) by mx1.FreeBSD.org (Postfix) with ESMTP id F2BC743D48; Fri, 27 May 2005 07:16:25 +0000 (GMT) (envelope-from owner-freebsd-questions@freebsd.org) Received: from [82.69.255.50] (helo=rtxnetworks.co.uk) by heisenberg.zen.co.uk with esmtp (Exim 4.30) id 1DbZ4z-0006Yt-0w; Fri, 27 May 2005 07:16:25 +0000 Received: from mail pickup service by rtxnetworks.co.uk with Microsoft SMTPSVC; Fri, 27 May 2005 08:16:07 +0100 thread-index: AcVii/N/a0VM1WOjSqS7anaqZlFJ7g== X-Original-To: freebsd-questions@FreeBSD.org Delivered-To: freebsd-questions@FreeBSD.org Date: Fri, 27 May 2005 08:16:07 +0100 From: "Don Lewis" To: In-Reply-To: <4295CC7C.3080009@cs.earlham.edu> Message-ID: <000001c5628b$f37feab0$144da8c0@rtxnetworks.local> MIME-Version: 1.0 Content-Type: TEXT/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list X-Mailer: Microsoft CDO for Exchange 2000 Sender: Errors-To: owner-freebsd-questions@freebsd.org X-Zen-Test-Spam-Score: 1 X-Zen-Test-Spam-Bar: (/) X-Originating-Schroedinger-IP: [216.136.204.119] X-Envelope-From: owner-freebsd-questions@freebsd.org X-Envelope-To: james@rtxnetworks.co.uk X-Apparently-To: james@rtxnetworks.co.uk Content-Class: urn:content-classes:message X-Zen-Loop: 4e5e9d7b303bfa0036200918db506edf Importance: normal X-Zen-Stored: julia.zen.co.uk/1DbZ3l-0002vI-5C/2005-05-27 07:15:09 Priority: normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.181 X-OriginalArrivalTime: 27 May 2005 07:16:07.0734 (UTC) FILETIME=[F3A15560:01C5628B] X-Originating-Heisenberg-IP: [82.69.255.50] Cc: freebsd-stable@FreeBSD.org, 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: Fri, 27 May 2005 07:16:26 -0000 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-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"