Date: Sat, 2 Jan 2010 18:50:52 -0500 (EST) From: Rick Macklem <rmacklem@uoguelph.ca> To: Jeremie Le Hen <jeremie@le-hen.org> Cc: Rick Macklem <rmacklem@FreeBSD.org>, freebsd-stable@FreeBSD.org Subject: Re: Cannot list a particular directory through NFS with UDP Message-ID: <Pine.GSO.4.63.1001021846270.19052@muncher.cs.uoguelph.ca> In-Reply-To: <20100102093617.GP84457@felucia.tataz.chchile.org> References: <20091213230650.GA45540@felucia.tataz.chchile.org> <Pine.GSO.4.63.0912181518280.9495@muncher.cs.uoguelph.ca> <20091229125603.GC84457@felucia.tataz.chchile.org> <Pine.GSO.4.63.0912311419170.22403@muncher.cs.uoguelph.ca> <20100102093617.GP84457@felucia.tataz.chchile.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 2 Jan 2010, Jeremie Le Hen wrote: > > I will reduce the MTU and see if the problem arises with directories > that could be read correctly otherwise. I will keep you informed. > You can reduce rsize to 1024, so that it isn't happening, but that will also change the size of the readdir reply. (ie. It might make the problem go away, but doesn't prove that IP fragmentation is the cause..) > Does NFS permit to fragment/reassemble at the application layer? > Nope. IP fragment reassembly should work fine and IP fragmentation happens all the time when using NFS over UDP. (Some would say NFS over UDP misused/abused IP fragmentation. In any case, it happens more frequently there than anywhere else.) >> ps: I vaguely recall that the problem went away when you used TCP >> instead. Is that correct? > > Yes this is correct. > Thanks for poking at this, rick
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.63.1001021846270.19052>