On Jul 22, 2009, at 5:47 PM, Trond Myklebust wrote:
> 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.
Yeah - has anything been submitted for 4.2 to fix this? (a readdir
cookie - like thingie)
>
>
> An alternative would be to let the server choose the
> max_rqst_sz/max_resp_sz by always requesting the maximum allowed
> value.
OK - maximum allowed value instead of maximum client supported value...
>
> Trond
>
On Wed, 2009-07-22 at 18:03 -0400, Andy Adamson wrote:
> On Jul 22, 2009, at 5:47 PM, Trond Myklebust wrote:
> > Well.... The rsize/wsize is one thing, but how about acls? We simply
> > don't know how big they may become.
>
> Yeah - has anything been submitted for 4.2 to fix this? (a readdir
> cookie - like thingie)
Not really. You pretty much have to set ACLs atomically, or you may end
up with security issues.
The good news is, though, that we should be able to figure out an upper
limit by looking at the max_rqst_sz/max_resp_sz that the server wants to
set.