From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Brent Clements <bclem@rice.edu>
Cc: nfs@lists.sourceforge.net
Subject: Re: 32k NFS blocksize not working
Date: 12 Mar 2003 23:41:59 +0100 [thread overview]
Message-ID: <shsy93kky14.fsf@charged.uio.no> (raw)
In-Reply-To: <1047506146.6666.11.camel@batman.ece.rice.edu>
>>>>> " " == Brent Clements <bclem@rice.edu> writes:
> We have a linux server running 2.4.20 plus it has nfsv3 udp/tcp
> server support compiled in.
> We have a linux client running 2.4.20 plus it has nfsv3 udp/tcp
> client support compiled.
> If we specify a read/write size above 8192 on the client, and
> then mount the nfs directory. It gives us the following on
> /proc/mounts
> cluster:/usr/local/ /tmp/d nfs
> rw,v3,rsize=8192,wsize=8192,hard,udp,lock,addr=cluster 0 0
> Do we have to edit something in a kernel include file to allow
> NFSV3 to mount above 8k?
You'll have to find a server which supports it. Linux 2.4.x knfsd as
it stands, supports only 8k, and so the client will override any
attempt that you make to set either rsize or wsize > 8k.
If you are feeling brave, you might try to change the value of
NFSSVC_MAXBLKSIZE in include/linux/nfsd/const.h and recompiling the
server.
Cheers,
Trond
-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open!
Get cracking and register here for some mind boggling fun and
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2003-03-12 22:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-12 17:09 NFS Client turning parameters? Brent Clements
2003-03-12 21:55 ` 32k NFS blocksize not working Brent Clements
2003-03-12 22:22 ` Dan Brunner
2003-03-12 22:41 ` Trond Myklebust [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=shsy93kky14.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=bclem@rice.edu \
--cc=nfs@lists.sourceforge.net \
/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.