From owner-freebsd-fs@FreeBSD.ORG Tue Jan 18 14:11:53 2011 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 7CEA91065670 for ; Tue, 18 Jan 2011 14:11:53 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id 34B5F8FC15 for ; Tue, 18 Jan 2011 14:11:52 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApwEAH8uNU2DaFvO/2dsb2JhbACEC6FBsmePHYEkgzh0BIRvhi8 X-IronPort-AV: E=Sophos;i="4.60,339,1291611600"; d="scan'208";a="107468849" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-jnhn-pri.mail.uoguelph.ca with ESMTP; 18 Jan 2011 09:11:52 -0500 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 5D7D7B3F58; Tue, 18 Jan 2011 09:11:52 -0500 (EST) Date: Tue, 18 Jan 2011 09:11:52 -0500 (EST) From: Rick Macklem To: Attila Nagy Message-ID: <1571522098.399734.1295359912372.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <4C614A7D.8030509@fsn.hu> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.203] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - IE8 (Win)/6.0.10_GA_2692) 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: Tue, 18 Jan 2011 14:11:53 -0000 > On 08/08/2010 02:06 AM, Rick Macklem wrote: > >> 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?). > I don't know whether this counts or not, but I've tried with an old > Solaris (x86) 8 (uname says it's Generic_108529-06). > > > ps: I don't recall the previous emails mentioning that the "ls" > > was ok for a solaris client. > > > It was in 4C582968.9000303@fsn.hu: > "I've mounted the share from an old Solaris box, which sees the file." > > This means, when I issue an ls | grep problematic_fname, I can see the > filename. > BTW, this turned out to be incorrect, because I've tested with the > same > (one of the missing) filename. > Doing a find . in the directory on both FreeBSD and Solaris client > shows > some differences. > So what I have now is: both the normal and the experimental NFSD show > the problem on both FreeBSD and Solaris clients (only the missing file > names are different). > > On Solaris there are 78 files missing, on FreeBSD there are 193, I > haven't checked that they are persistent across reboots or not. I believe that this problem might be fixed by r216774 in head (for the regular NFS server) and r216691 in head (for the experimental NFS server). The above patches fixes a problem that would occur when ZFS generated non monotonically increasing directory offset cookies and readdir in the server would skip over some directory entries. rick