On Fri, 2009-05-08 at 22:37 +0200, André Berger wrote: > * Chuck Lever (2009-05-08): > > On May 8, 2009, at 3:38 PM, André Berger wrote: > >> * André Berger (2009-04-21): > >>> * Chuck Lever (2009-04-20): > >>>> On Apr 20, 2009, at 5:14 AM, André Berger wrote: > >>>>> * Chuck Lever (2009-04-17): > [...] > > Assuming 192.168.1.8 is your server, frame 79 and 622 report FSINFO > > results: > > > > Network File System, FSINFO Reply > > [Program Version: 3] > > [V3 Procedure: FSINFO (19)] > > Status: NFS3_OK (0) > > obj_attributes > > attributes_follow: no value (0) > > rtmax: 16384 > > rtpref: 16384 > > rtmult: 4096 > > wtmax: 16384 > > wtpref: 16384 > > wtmult: 4096 > > dtpref: 4096 > > maxfilesize: 2194719883264 > > time delta: 1.000000000 seconds > > seconds: 1 > > nano seconds: 0 > > Properties: 0x0000001b > > 1... . = SETATTR can set time on server > > .1.. . = PATHCONF is valid for all files > > ...1 . = File System supports symbolic links > > .... 1 = File System supports hard links > > > > says your server operating system supports NFS rsize and wsize maxima of > > 16384 bytes. > > > > RFC 1813: > >> rtmax > >> The maximum size in bytes of a READ request supported by the server. > >> Any READ with a number greater than rtmax will result in a short read of > >> rtmax bytes or less. > > My OS is 2.6.29.2, Debian etch, on a PPC system. I swear I got 32K > [rw]size with kernels < 2.6.19, at least "mount" reported them as > such. With recent kernels, "mount" and your analysis agree on just > 16K. So, what can I do? There is nothing the client can do as long as the server says it won't accept NFS requests with read or write sizes > 16k. You therefore need to fix the server. Trond -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
