All of lore.kernel.org
 help / color / mirror / Atom feed
From: "André Berger" <andre.berger-S0/GAf8tV78@public.gmane.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
	Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Subject: Re: NFS issues with recent kernels [long]
Date: Fri, 8 May 2009 22:37:51 +0200	[thread overview]
Message-ID: <20090508203751.GD3801@fuchs> (raw)
In-Reply-To: <8D7394C9-0142-4635-88E5-139F4F5F39F6@oracle.com>

* Chuck Lever (2009-05-08):
> On May 8, 2009, at 3:38 PM, Andr=E9 Berger wrote:
>> * Andr=E9 Berger (2009-04-21):
>>> * Chuck Lever (2009-04-20):
>>>> On Apr 20, 2009, at 5:14 AM, Andr=E9 Berger wrote:
>>>>> * Chuck Lever (2009-04-17):
[...]
> Assuming 192.168.1.8 is your server, frame 79 and 622 report FSINFO =20
> 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... . =3D SETATTR can set time on server
>         .1.. . =3D PATHCONF is valid for all files
>         ...1 . =3D File System supports symbolic links
>         .... 1 =3D File System supports hard links
>
> says your server operating system supports NFS rsize and wsize maxima=
 of=20
> 16384 bytes.
>
> RFC 1813:
>> rtmax
>> The maximum size in bytes of a READ request supported by the server.=
 =20
>> Any READ with a number greater than rtmax will result in a short rea=
d of=20
>> 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?

-Andr=E9

--=20
May as well be hung for a sheep as a lamb!
Linkstation/KuroBox/HG/HS/Tera Kernel 2.6/PPC from <http://hvkls.dyndns=
=2Eorg>
iPhone <http://hvkls.dyndns.org/downloads/documentation/README-iphone.h=
tml>

  reply	other threads:[~2009-05-08 20:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-17 10:27 NFS issues with recent kernels [long] André Berger
2009-04-17 16:29 ` Chuck Lever
2009-04-17 16:29   ` Chuck Lever
     [not found]   ` <20090420091454.GB614@fuchs>
2009-04-20 19:07     ` Chuck Lever
2009-04-21  4:36       ` André Berger
     [not found]         ` <20090508193813.GC3801@fuchs>
2009-05-08 20:00           ` Chuck Lever
2009-05-08 20:37             ` André Berger [this message]
2009-05-08 20:48               ` Trond Myklebust
     [not found]                 ` <1241815735.7291.1.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-05-09 18:57                   ` André Berger
2009-05-09 20:41                     ` Trond Myklebust
     [not found]                       ` <1241901691.5101.26.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-05-12  5:42                         ` André Berger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090508203751.GD3801@fuchs \
    --to=andre.berger-s0/gaf8tv78@public.gmane.org \
    --cc=chuck.lever@oracle.com \
    --cc=g.liakhovetski@gmx.de \
    --cc=linux-nfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.