From owner-freebsd-current Wed Jul 19 08:53:41 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id IAA28907 for current-outgoing; Wed, 19 Jul 1995 08:53:41 -0700 Received: from minnow.render.com (render.demon.co.uk [158.152.30.118]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id IAA28899 for ; Wed, 19 Jul 1995 08:53:33 -0700 Received: (from dfr@localhost) by minnow.render.com (8.6.9/8.6.9) id QAA24889; Wed, 19 Jul 1995 16:53:26 +0100 Date: Wed, 19 Jul 1995 16:53:25 +0100 (BST) From: Doug Rabson To: Peter Wemm cc: freebsd-current@freebsd.org Subject: Re: what's going on here? (NFSv3 problem?) In-Reply-To: <3uj6pg$3h3$1@haywire.DIALix.COM> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@freebsd.org Precedence: bulk On 19 Jul 1995, Peter Wemm wrote: > Some time in the last few weeks, doing a ls on a large NFS mounted > directory.. It looks like the server is answering with the wrong > offset, but it used to work and the server hasn't changed lately > (like, years... It's a vintage SVR4.0/386 system.) > > The freebsd client has it mounted with a read and write size of 1024, > which struck me as odd that it appears to be asking for a 8192 byte > chunk... It works fine with directory scans of smaller directories.. > > And yes, I'm just about to run fsirand on the server.. :-) > > Puzzled, (I don't speak NFS, so please be gentle.. ;-) > -Peter > I just checked and it appears that the size used for readdir requests (NFS_DIRBLKSIZE) has increased from 1024 to 4096 in the nfsv3 change. I am not sure why though. It is also a bit confusing that you are seeing 8k readdir requests - from the looks of it, they should be 4k. Try reducing NFS_DIRBLKSIZE in to 1024 and see if it fixes your problem. -- Doug Rabson, Microsoft RenderMorphics Ltd. Mail: dfr@render.com Phone: +44 171 251 4411 FAX: +44 171 251 0939