From mboxrd@z Thu Jan 1 00:00:00 1970 From: Trond Myklebust Subject: Re: nfsroot 8k block size Date: Mon, 09 May 2005 08:33:05 -0400 Message-ID: <1115641985.24625.8.camel@lade.trondhjem.org> References: <427F45C3.1060005@bladefusion.com> <1115638990.24625.2.camel@lade.trondhjem.org> <427F4F4D.40600@bladefusion.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: linux-fsdevel@vger.kernel.org Return-path: Received: from pat.uio.no ([129.240.130.16]:674 "EHLO pat.uio.no") by vger.kernel.org with ESMTP id S261324AbVEIMdU convert rfc822-to-8bit (ORCPT ); Mon, 9 May 2005 08:33:20 -0400 To: Aleksey Senin In-Reply-To: <427F4F4D.40600@bladefusion.com> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org m=C3=A5 den 09.05.2005 Klokka 14:53 (+0300) skreiv Aleksey Senin: > Yes. If I boot client from the disk with the same kernel, I can mount= =20 > directory /bla/bla/bla with block size 32k, it meant the command > mount -t nfs -o rsize=3D32768,wsize=3D32768 XXX:/bla/bla/bla /tmp/cli= ent > work fine. > I'm using kernel 2.4.25 on the server side, and kernel 2.4.30 on the=20 > client side. Only the 2.6 kernels support 32k by default. knfsd in kernel 2.4.25 onl= y supports 8k r/wsizes unless you have been applying special patches. How are you checking that the block size is indeed being set to 32k on the client? Note that /etc/fstab will lie: it just repeats your command line. The only way to really check is to use tcpdump or ethereal. Cheers, Trond - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel= " in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html