From owner-freebsd-fs@FreeBSD.ORG Wed Aug 11 03:15:09 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 CA6061065678 for ; Wed, 11 Aug 2010 03:15:09 +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 822278FC24 for ; Wed, 11 Aug 2010 03:15:09 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApwEAJOyYUyDaFvO/2dsb2JhbACDFZ4Oqy+SAoEmgyFzBIlA X-IronPort-AV: E=Sophos;i="4.55,350,1278302400"; d="scan'208";a="87996372" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-annu-pri.mail.uoguelph.ca with ESMTP; 10 Aug 2010 23:15:08 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 8917BB3F2A; Tue, 10 Aug 2010 23:15:08 -0400 (EDT) Date: Tue, 10 Aug 2010 23:15:08 -0400 (EDT) From: Rick Macklem To: Attila Nagy Message-ID: <853573529.515333.1281496508531.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: [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: Wed, 11 Aug 2010 03:15:09 -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 [stuff snipped] > 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. Ok, so it seems to be a server issue. Since there are quite a few files missing, I'm surprised others aren't seeing problmes? I suspect it is some interaction between ZFS and the NFS server that is causing this, but that's just a hunch. Possibly a problem w.r.t. how the directory offset cookies are handled. Can you conveniently move the directory to a UFS2 volume and export that, to see if the problem then goes away? Also, what architecture is the server running? (I'm wondering if it might be an endianness or 32/64 bit issue related to the directory offset cookies.? Just wild guesses at this point.) If you can't move the directory to UFS2 or that doesn't fix the problem, all I can think to do is write/run a little program locally on the server that does getdirentries() on the directory, to try and spot something that might confuse the NFS server. (I can write such a program for you, but I'd like to hear if it is a ZFS specific problem first. rick