From owner-freebsd-fs@FreeBSD.ORG Sat Aug 7 00:35:35 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 71AC11065675 for ; Sat, 7 Aug 2010 00:35:35 +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 28B6E8FC08 for ; Sat, 7 Aug 2010 00:35:34 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApwEANdGXEyDaFvO/2dsb2JhbACDFZ4ntC+RfIEmgyFzBIk3 X-IronPort-AV: E=Sophos;i="4.55,331,1278302400"; d="scan'208";a="87611589" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-annu-pri.mail.uoguelph.ca with ESMTP; 06 Aug 2010 20:35:34 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 290A6B3EA3; Fri, 6 Aug 2010 20:35:34 -0400 (EDT) Date: Fri, 6 Aug 2010 20:35:34 -0400 (EDT) From: Rick Macklem To: Markus Gebert Message-ID: <507225020.401114.1281141334084.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: Sat, 07 Aug 2010 00:35:35 -0000 > Subject: Re: NFS problem: file doesn't appear in file listing, but can be accessed directly > On 03.08.2010, at 16:36, Attila Nagy wrote: > > >> You can try replacing the client and server with the experimental > >> ones and see if that fixes the problem. > >> For the client: mount with "-t newnfs" instead of "-t nfs" > >> For the server: start both mountd and nfsd with the "-e" option > > Sure. It works with the newnfs client, so it must be either a weird > > interaction between the FreeBSD server and client (old), or a client > > bug. > > Have you tried comparing on-the-wire NFS requests and responses > between newnfs and legacy nfs clients for your test case? Maybe you > can rule out the former like this. Or at least prove that the server > actually responds correctly to the READDIR request. > Well, I looked at a packet capture emailed to me by Attila Nagy and the filename shows up in the Lookup near the end (the "ls -la"), but is not in any of the readdir replies (a search from the start of the capture in wireshark only finds it at the Lookup). Therefore, I think the problem is w.r.t. the server. (He did this failed case with the "newnfs", so both clients see the problem.) Attila, could you by any chance try switching to the experimental server ("-e" on both mountd and nfsd) and see if the problem persists? (The experimental server may replace the regular one relatively soon, so if the problem doesn't exist in the experimental one, I'm tempted to leave it at that. If both servers have a problem, it definitely needs further investigation.) rick