From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Andy Adamson <andros@netapp.com>
Cc: Ben Greear <greearb@candelatech.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-nfs@vger.kernel.org
Subject: Re: Error mounting FC8 NFS server with 2.6.31-rc3 NFSv4 client.
Date: Wed, 22 Jul 2009 17:47:16 -0400 [thread overview]
Message-ID: <1248299236.9202.3.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <74713B5B-DF7F-4357-AE3A-0F6B44C41116@netapp.com>
On Wed, 2009-07-22 at 17:32 -0400, Andy Adamson wrote:
> nfs4_init_session should simply return if the nfs_client cl_cons_state
> is not NFS_CS_SESSION_INITING.
> I shouldn't be trying to set the session max_resp_sz/max_rqst_sz to
> the rsize/wsize, but rather to the maximum rsize/wsize supported by
> the client.
> If the server accepts or increases the max_resp_sz/max_rqst_sz then
> all is well.
> If the server reduces the max_resp_sz/max_rqst_sz, the maximum rsize/
> wsize available for NFSv4.1 partition mounts to the server needs to be
> reduced accordingly. So the nfs_server rsize/wsize needs to be bound
> by the session max_resp_sz/max_rqst_sz as well as by the maximum
> supported size.
Well.... The rsize/wsize is one thing, but how about acls? We simply
don't know how big they may become.
An alternative would be to let the server choose the
max_rqst_sz/max_resp_sz by always requesting the maximum allowed value.
Trond
next prev parent reply other threads:[~2009-07-22 21:47 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-20 22:09 Ben Greear
2009-07-21 12:15 ` Trond Myklebust
2009-07-21 16:49 ` Ben Greear
2009-07-21 17:12 ` Trond Myklebust
2009-07-21 17:36 ` Ben Greear
2009-07-21 17:59 ` Trond Myklebust
2009-07-21 18:01 ` Ben Greear
2009-07-21 18:28 ` Trond Myklebust
2009-07-21 18:32 ` Ben Greear
2009-07-21 18:54 ` Trond Myklebust
2009-07-21 19:57 ` Frans Pop
2009-07-21 21:17 ` Trond Myklebust
2009-07-21 21:48 ` Trond Myklebust
2009-07-21 21:50 ` Ben Greear
2009-07-22 19:49 ` Andy Adamson
2009-07-22 20:20 ` Trond Myklebust
2009-07-22 21:32 ` Andy Adamson
2009-07-22 21:47 ` Trond Myklebust [this message]
2009-07-22 22:03 ` Andy Adamson
2009-07-22 22:17 ` Trond Myklebust
2009-07-22 22:26 ` Andy Adamson
2009-07-21 19:23 ` Frans Pop
2009-07-21 19:54 ` Trond Myklebust
2009-07-21 20:24 ` Frans Pop
2009-07-21 17:49 ` Frans Pop
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=1248299236.9202.3.camel@heimdal.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=andros@netapp.com \
--cc=greearb@candelatech.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®