From owner-freebsd-fs@FreeBSD.ORG Fri Aug 13 02:26:40 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 D9B621065695 for ; Fri, 13 Aug 2010 02:26:40 +0000 (UTC) (envelope-from jonathan@kc8onw.net) Received: from mail.kc8onw.net (kc8onw.net [206.55.209.81]) by mx1.freebsd.org (Postfix) with ESMTP id B707E8FC15 for ; Fri, 13 Aug 2010 02:26:40 +0000 (UTC) Received: from [10.70.3.198] (c-98-223-164-104.hsd1.in.comcast.net [98.223.164.104]) by mail.kc8onw.net (Postfix) with ESMTPSA id AAD171B997; Thu, 12 Aug 2010 22:07:26 -0400 (EDT) Message-ID: <4C64A8D3.3090706@kc8onw.net> Date: Thu, 12 Aug 2010 22:07:15 -0400 From: Jonathan User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Lightning/1.0b2 Thunderbird/3.1.2 MIME-Version: 1.0 To: Attila Nagy References: <4C5810D6.9060605@fsn.hu> <4C582533.4070009@fsn.hu> In-Reply-To: <4C582533.4070009@fsn.hu> Content-Type: text/plain; charset=ISO-8859-2; 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: Fri, 13 Aug 2010 02:26:40 -0000 Just a note but I ran into a problem like this with ZFS and Samba a few years back http://www.mail-archive.com/freebsd-stable@freebsd.org/msg92482.html I don't if it's related but it's probably worth checking. Jonathan On 8/3/2010 10:18 AM, Attila Nagy wrote: > On 08/03/10 14:51, Attila Nagy wrote: >> 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... > Additional info: > - upgrading the client to 8-STABLE doesn't help > - rebooting the client doesn't help > - on the server side, there is zfs beneath the mount