From: Brent Clements Subject: 32k NFS blocksize not working Date: 12 Mar 2003 15:55:46 -0600 Sender: nfs-admin@lists.sourceforge.net Message-ID: <1047506146.6666.11.camel@batman.ece.rice.edu> References: <1047488992.6343.2.camel@batman.ece.rice.edu> Mime-Version: 1.0 Content-Type: text/plain Cc: nfs@lists.sourceforge.net Return-path: Received: from handler2.mail.rice.edu ([128.42.58.202]) by sc8-sf-list1.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 18tEA3-00012E-00 for ; Wed, 12 Mar 2003 13:53:19 -0800 To: Brent Clements In-Reply-To: <1047488992.6343.2.camel@batman.ece.rice.edu> Errors-To: nfs-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Id: Discussion of NFS under Linux development, interoperability, and testing. List-Unsubscribe: , List-Archive: 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? Thanks, Brent ------------------------------------------------------- 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