From owner-freebsd-fs@FreeBSD.ORG Tue Aug 3 14:36:39 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 52229106566B for ; Tue, 3 Aug 2010 14:36:39 +0000 (UTC) (envelope-from bra@fsn.hu) Received: from people.fsn.hu (people.fsn.hu [195.228.252.137]) by mx1.freebsd.org (Postfix) with ESMTP id AD58A8FC29 for ; Tue, 3 Aug 2010 14:36:38 +0000 (UTC) Received: by people.fsn.hu (Postfix, from userid 1001) id E77E33BA5F6; Tue, 3 Aug 2010 16:36:36 +0200 (CEST) X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.2 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MF-ACE0E1EA [pR: 17.4355] X-CRM114-CacheID: sfid-20100803_16362_43A39A40 X-CRM114-Status: Good ( pR: 17.4355 ) X-DSPAM-Result: Whitelisted X-DSPAM-Processed: Tue Aug 3 16:36:36 2010 X-DSPAM-Confidence: 0.8516 X-DSPAM-Probability: 0.0000 X-DSPAM-Signature: 4c582974615151562336186 X-DSPAM-Factors: 27, From*Attila Nagy , 0.00096, FreeBSD, 0.00254, FreeBSD, 0.00254, wrote, 0.00263, >+>, 0.00519, >+>, 0.00519, patch, 0.00794, fsn+hu>, 0.00823, flags, 0.01000, see+if, 0.01000, it's+the, 0.01000, STABLE, 0.01000, ls, 0.01000, ls, 0.01000, reproduce, 0.01000, Subject*file, 0.01000, Subject*file, 0.01000, I've+tried, 0.01000, wrote+>>, 0.01000, Subject*can+be, 0.99000, ZFS, 0.01000, >+You, 0.01000, >+For, 0.01000, >+For, 0.01000, it+>, 0.01000, one+is, 0.01000, X-Spambayes-Classification: ham; 0.00 Message-ID: <4C582968.9000303@fsn.hu> Date: Tue, 03 Aug 2010 16:36:24 +0200 From: Attila Nagy User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.23) Gecko/20090817 Thunderbird/2.0.0.23 Mnenhy/0.7.6.0 MIME-Version: 1.0 To: Rick Macklem References: <1147918452.245970.1280844811813.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <1147918452.245970.1280844811813.JavaMail.root@erie.cs.uoguelph.ca> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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, 03 Aug 2010 14:36:39 -0000 On 08/03/2010 04:13 PM, Rick Macklem wrote: >> From: "Attila Nagy" >> To: freebsd-fs@freebsd.org >> Sent: Tuesday, August 3, 2010 8:51:34 AM >> Subject: NFS problem: file doesn't appear in file listing, but can be accessed directly >> Hello, >> >> I have two FreeBSD 8.x machines, one is the NFS server (8-STABLE, >> about >> one week old), the other is the client (8.1-PRERELEASE from May). >> >> The strange thing is this, happening on the NFS mount, client side: >> # ls -la 1083536654.80433.be03,S=7592 >> -rw------- 1 mail mail 7592 May 3 2004 1083536654.80433.be03,S=7592 >> # ls | grep 1083536654 >> ls doesn't find that file... >> >> Are there any known bugs regarding bad NFS client behaviour (caching >> maybe) in the above timeframe in stable/8? >> The machine does high amounts of NFS copying, and I can reproduce the >> above any time, so if it's cache related, it's pretty weird... >> >> I'm currently upgrading to see whether that helps. >> > The only thing I am aware of the "might" cause this is a bug > in the regular server when used with ZFS and the client uses > the "rdriplus" option (pjd has a patch, but I don't think it > has ever been committed). > > So, if your mount uses the "rdirplus" option, try it without that. The mount is used with this: be01:/home/hm01 /home/hm01 nfs rw 0 0 So no special flags. I've tried with rdirplus anyways (maybe it's the opposite), the file can't be seen. I've mounted the share from an old Solaris box, which sees the file. > Otherwise, I suspect that it is a bug in either the client or server. > > 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.