From owner-freebsd-current Fri Jul 21 01:49:45 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id BAA16373 for current-outgoing; Fri, 21 Jul 1995 01:49:45 -0700 Received: from sunny.bog.msu.su (sunny.bog.msu.su [158.250.20.1]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id BAA16364 for ; Fri, 21 Jul 1995 01:49:39 -0700 Received: (from dima@localhost) by sunny.bog.msu.su (8.6.12/8.6.12) id MAA09471; Fri, 21 Jul 1995 12:47:23 +0400 Date: Fri, 21 Jul 1995 12:47:18 +0400 (????) From: Dmitry Khrustalev To: current@FreeBSD.ORG Subject: Re: what's going on here? (NFSv3 problem?) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.ORG Precedence: bulk On Fri, 21 Jul 1995, Doug Rabson wrote: >No, the bug is that nfs_readdir is making larger protocol requests than >it used to and the server is puking. NFSv3 allows the server to hint at >a size to use. I don't have the rfc for NFSv2 handy so I can't check. >It is possible that we are violating the protocol here. It is also >possible that the SVR4 server is returning crap data. Very possible. Sun has simular problem with SunOS 5.4 - it is the first version using 8k readdirs and it is known to fail on Ultrix and SunOS 3.5 servers. Their solution is system wide option limiting readdir size. -Dima