From owner-freebsd-current@FreeBSD.ORG Fri Apr 2 16:07:43 2004 Return-Path: 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 B2F5916A4CE for ; Fri, 2 Apr 2004 16:07:43 -0800 (PST) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6557443D2D for ; Fri, 2 Apr 2004 16:07:43 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.12.10/8.12.10) id i3307g1v057426; Fri, 2 Apr 2004 18:07:42 -0600 (CST) (envelope-from dan) Date: Fri, 2 Apr 2004 18:07:42 -0600 From: Dan Nelson To: Sean McNeil Message-ID: <20040403000742.GD49311@dan.emsphone.com> References: <1080882894.5980.26.camel@server.mcneil.com> <20040402163353.GC6724@dan.emsphone.com> <1080940409.3711.1.camel@server.mcneil.com> <20040402215745.GB49311@dan.emsphone.com> <1080949413.49158.27.camel@server.mcneil.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1080949413.49158.27.camel@server.mcneil.com> X-OS: FreeBSD 5.2-CURRENT X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i cc: freebsd-current@freebsd.org Subject: Re: nfs server issues X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Sat, 03 Apr 2004 00:07:43 -0000 In the last episode (Apr 02), Sean McNeil said: > On Fri, 2004-04-02 at 13:57, Dan Nelson wrote: > > In the last episode (Apr 02), Sean McNeil said: > > > OK, here is a tcpdump. It is confusing. It looks like after the > > > first fragment is received it is looking up some bazaar IP > > > address.... > > > > > > 13:02:57.566952 free.mcneil.com.1360032988 > server.mcneil.com.nfs: 136 readdir fh 1002,54097/7890231 4096 bytes @ 0x000000000 (DF) > > > 13:02:57.567266 server.mcneil.com.nfs > free.mcneil.com.1360032988: reply ok 1472 readdir (frag 1645:1480@0+) > > > 13:02:57.567268 0.0.0.1 > 0.0.10.7: (frag 1645:4@1480) > > > > Weird. Is this at the server or the client? > > This is a client-side dump. Both server and client have MTU of 1500. > > Server side says: > > 15:37:44.292564 IP free.mcneil.com.851449566 > server.mcneil.com.nfs: 136 readdir fh 1002,54097/7890231 4096 bytes @ 0x0 > 15:37:44.292705 IP server.mcneil.com.nfs > free.mcneil.com.851449566: reply ok 1472 readdir > 15:37:44.292711 IP server.mcneil.com > free.mcneil.com: udp > > Is there something in a packet that tells rpc/nfs to reassemble with > something other than the source/destination info? Neither RPC or NFS are involved with fragmentation. That's all done at the UDP level. I wonder if it's a NIC problem. Can you try a different card (maybe even a different brand of card if possible)? another interesting test would be to get a hub and a 3rd machine, then do dumps with the hub on the server's port, and then the client's port. If you get garbled frags in both places, I'd lean toward a NIC problem on the server. If your card supports checksum offloading, try disabling it (ifconfig xx0 -rxcsum -txcsum). -- Dan Nelson dnelson@allantgroup.com