All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shehjar Tikoo <shehjart-iP+wyIN8Xge1Z/+hSey0Gg@public.gmane.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: Different rsize/wsize for different NFS server software
Date: Tue, 12 May 2009 20:53:40 +0530	[thread overview]
Message-ID: <4A09947C.9030206@zresearch.com> (raw)
In-Reply-To: <1242137345.21939.6.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>

Trond Myklebust wrote:
> On Tue, 2009-05-12 at 19:17 +0530, Shehjar Tikoo wrote:
>> Shehjar Tikoo wrote:
...
...
...
>> Is there any way to force the client to use a 64k wsize value?
> 
> You probably have the exact same filesystem still mounted somewhere else
> on that client. A 2.6.18 kernel will, in those circumstances, share the
> same super block with both mount points, and will therefore not permit
> you to use different mount options.

That was, in fact, the case.

Thanks
Shehjar

> 
> This is something which has been fixed in more recent kernels.
> 

> Trond
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


      parent reply	other threads:[~2009-05-12 15:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-12 11:14 Different rsize/wsize for different NFS server software Shehjar Tikoo
     [not found] ` <4A0959F9.1010107-iP+wyIN8Xge1Z/+hSey0Gg@public.gmane.org>
2009-05-12 13:47   ` Shehjar Tikoo
     [not found]     ` <4A097DE9.6030709-iP+wyIN8Xge1Z/+hSey0Gg@public.gmane.org>
2009-05-12 14:09       ` Trond Myklebust
     [not found]         ` <1242137345.21939.6.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-05-12 15:23           ` Shehjar Tikoo [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=4A09947C.9030206@zresearch.com \
    --to=shehjart-ip+wyin8xge1z/+hsey0gg@public.gmane.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond.myklebust@fys.uio.no \
    /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.