From owner-freebsd-fs@FreeBSD.ORG Sun Aug 8 00:06:49 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CD21C1065674 for ; Sun, 8 Aug 2010 00:06:49 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.mail.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id 83EB48FC08 for ; Sun, 8 Aug 2010 00:06:49 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApwEAE+RXUyDaFvO/2dsb2JhbACDFZ4nsESQdoEmgyFzBIk7 X-IronPort-AV: E=Sophos;i="4.55,336,1278302400"; d="scan'208";a="87671541" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-annu-pri.mail.uoguelph.ca with ESMTP; 07 Aug 2010 20:06:45 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 9F54B9210F; Sat, 7 Aug 2010 20:06:47 -0400 (EDT) Date: Sat, 7 Aug 2010 20:06:47 -0400 (EDT) From: Rick Macklem To: Markus Gebert Message-ID: <163511110.410136.1281226007565.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [24.65.230.102] X-Mailer: Zimbra 6.0.7_GA_2476.RHEL4 (ZimbraWebClient - SAF3 (Mac)/6.0.7_GA_2473.RHEL4_64) Cc: freebsd-fs@freebsd.org Subject: Re: NFS problem: file doesn't appear in file listing, but can be accessed directly X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Aug 2010 00:06:50 -0000 > On 07.08.2010, at 02:35, Rick Macklem wrote: > > I agree, this must be some kind of server issue then. Still, I wonder > why the solaris client didn't show the problem... > > 2 things: 1 - the solaris client uses ReaddirPlus and not Readdir RPCs by default (I can't remember if that default can be overridden?). 2 - different size requests. The Readdir RPC request specifies the maximum size of a reply (including all XDR) and ReaddirPlus both that and a maximum size for the directory information (which is not defined by the RFC, so there is confusion over what that size actually is a?). When the solaris client specifies a different maximum sizes, that probably avoids the bug. (Since most "ls" listings for directories work, the bug is probably a miscalculation of this limit that results in the entry being missed, but that's just a guess??) rick ps: I don't recall the previous emails mentioning that the "ls" was ok for a solaris client.