From owner-freebsd-stable@FreeBSD.ORG Sat Jan 2 09:36:28 2010 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E31A61065670; Sat, 2 Jan 2010 09:36:28 +0000 (UTC) (envelope-from jeremie@le-hen.org) Received: from smtp1-g21.free.fr (smtp1-g21.free.fr [212.27.42.1]) by mx1.freebsd.org (Postfix) with ESMTP id CB53A8FC25; Sat, 2 Jan 2010 09:36:25 +0000 (UTC) Received: from smtp1-g21.free.fr (localhost [127.0.0.1]) by smtp1-g21.free.fr (Postfix) with ESMTP id A42F894018D; Sat, 2 Jan 2010 10:36:20 +0100 (CET) Received: from endor.tataz.chchile.org (tataz.chchile.org [82.233.239.98]) by smtp1-g21.free.fr (Postfix) with ESMTP id C90D79400CC; Sat, 2 Jan 2010 10:36:17 +0100 (CET) Received: from felucia.tataz.chchile.org (felucia.tataz.chchile.org [192.168.1.9]) by endor.tataz.chchile.org (Postfix) with ESMTP id BB8E133E85; Sat, 2 Jan 2010 09:36:17 +0000 (UTC) Received: by felucia.tataz.chchile.org (Postfix, from userid 1000) id AA4FEA1279; Sat, 2 Jan 2010 09:36:17 +0000 (UTC) Date: Sat, 2 Jan 2010 10:36:17 +0100 From: Jeremie Le Hen To: Rick Macklem Message-ID: <20100102093617.GP84457@felucia.tataz.chchile.org> References: <20091213230650.GA45540@felucia.tataz.chchile.org> <20091229125603.GC84457@felucia.tataz.chchile.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-stable@FreeBSD.org, Jeremie Le Hen , Rick Macklem Subject: Re: Cannot list a particular directory through NFS with UDP 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: Sat, 02 Jan 2010 09:36:29 -0000 Rick, Thanks for your time on this. On Thu, Dec 31, 2009 at 02:23:32PM -0500, Rick Macklem wrote: > [stuff snipped] > >> This appears to be the reply to the nfs readdir request, which is what > >> would be expected. It could be a problem with the content or the reply > >> or a NetBSD client issue. > >> > >> If you were to email me the raw tcpdump capture for the above, I could > >> take a look at it in wireshark (which knows how to interpret nfs) and > >> see if there is anything bogus looking in the reply. > >> ("tcpdump -s 0 -w host 192.168.1.1" and then email me as an > >> attachment, should do it) > > > > You will find the pcap file attached. > > > Well, I looked at it under wireshark and the readdir reply looks fine. > (It is made up of two IP fragments, but wireshark reassembles them ok > and says the checksums are ok. The contents look like a valid Readdir > RPC reply.) Maybe NetBSD doesn't reassemble the IP fragments correctly > or has an issue w.r.t. the checksum, but Wireshark thinks it's aok. I will reduce the MTU and see if the problem arises with directories that could be read correctly otherwise. I will keep you informed. Does NFS permit to fragment/reassemble at the application layer? > ps: I vaguely recall that the problem went away when you used TCP > instead. Is that correct? Yes this is correct. Regards, -- Jeremie Le Hen Humans are born free and equal. But some are more equal than the others. Coluche