public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "André Berger" <andre.berger-S0/GAf8tV78@public.gmane.org>
To: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Cc: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Subject: Re: NFS issues with recent kernels [long]
Date: Tue, 12 May 2009 07:42:25 +0200	[thread overview]
Message-ID: <20090512054225.GH3801@fuchs> (raw)
In-Reply-To: <1241901691.5101.26.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>

* Trond Myklebust (2009-05-09):
> On Sat, 2009-05-09 at 20:57 +0200, Andr=C3=A9 Berger wrote:
> > * Trond Myklebust (2009-05-08):
> > > On Fri, 2009-05-08 at 22:37 +0200, Andr=C3=A9 Berger wrote:
> > > > * Chuck Lever (2009-05-08):
> > > > > On May 8, 2009, at 3:38 PM, Andr=C3=A9 Berger wrote:
> > > > >> * Andr=C3=A9 Berger (2009-04-21):
> > > > >>> * Chuck Lever (2009-04-20):
> > > > >>>> On Apr 20, 2009, at 5:14 AM, Andr=C3=A9 Berger wrote:
> > > > >>>>> * Chuck Lever (2009-04-17):
> > > > [...]
> > > > > Assuming 192.168.1.8 is your server, frame 79 and 622 report =
=46SINFO =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 wsiz=
e 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 s=
hort read of=20
> > > > >> rtmax bytes or less.
> > > >=20
> > > > 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 j=
ust
> > > > 16K. So, what can I do?
> > >=20
> > > 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.
> >=20
> > So what can I do to fix this? I've upgraded to nfs-utils-1.1.4 in t=
he
> > meantime, 1.1.5 and both 1.1.6 give me=20
> >=20
> >   make[2]: Entering directory `/tmp/nfs-utils-1.1.5/support/misc'
> >   gcc -DHAVE_CONFIG_H -I. -I../../support/include   -I/usr/include =
 -D_GNU_SOURCE -Wall -Wstrict-prototypes  -pipe -g -O2 -MT tcpwrapper.o=
 -MD -MP -MF .deps/tcpwrapper.Tpo -c -o tcpwrapper.o tcpwrapper.c
> >   tcpwrapper.c: In function =E2=80=98haccess_add=E2=80=99:
> >   tcpwrapper.c:117: warning: implicit declaration of function =E2=80=
=98TAILQ_EMPTY=E2=80=99
> >   tcpwrapper.c:119: error: expected expression before =E2=80=98else=
=E2=80=99
> >   tcpwrapper.c: In function =E2=80=98haccess_lookup=E2=80=99:
> >   tcpwrapper.c:131: warning: implicit declaration of function =E2=80=
=98TAILQ_FOREACH=E2=80=99
> >   tcpwrapper.c:131: error: =E2=80=98list=E2=80=99 undeclared (first=
 use in this function)
> >   tcpwrapper.c:131: error: (Each undeclared identifier is reported =
only once
> >   tcpwrapper.c:131: error: for each function it appears in.)
> >   tcpwrapper.c:131: error: expected =E2=80=98;=E2=80=99 before =E2=80=
=98{=E2=80=99 token
> >   make[2]: *** [tcpwrapper.o] Error 1
> >   make[2]: Leaving directory `/tmp/nfs-utils-1.1.5/support/misc'
> >   make[1]: *** [all-recursive] Error 1
> >   make[1]: Leaving directory `/tmp/nfs-utils-1.1.5/support'
> >   make: *** [all-recursive] Error 1
> >=20
> > with=20
> >=20
> >   ./configure --prefix=3D/usr/local --sysconfdir=3D/etc --with-tcp-=
wrappers=3D/usr/include --with-statedir=3D/var/lib/nfs
> >=20
> > I've already upgraded tcpd to the Lenny version 7.6.q-16 (from
> > source), but that didn't help.=20
> >=20
> > With 1.1.4, I still get 16384 [rw]size while 32768 were requested.=20
>=20
>=20
> If the server is based on a recent Linux kernel, then you should chec=
k
> the value of /proc/fs/nfsd/max_block_size. If it is less than 32k, th=
en
> try increasing it.

Indeed, that does the trick with 2.6.29.3 :)

Thank you very much, everyone!

-Andr=C3=A9

--=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>

      parent reply	other threads:[~2009-05-12  5:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090417102659.GC55096@fuchs>
2009-04-17 16:29 ` NFS issues with recent kernels [long] 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
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 [this message]

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=20090512054225.GH3801@fuchs \
    --to=andre.berger-s0/gaf8tv78@public.gmane.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox