From owner-freebsd-current@FreeBSD.ORG Thu Nov 8 10:22:30 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 28B7B16A46D for ; Thu, 8 Nov 2007 10:22:30 +0000 (UTC) (envelope-from n-butcher=freebsd-current=freebsd.org=sbibybnr@fusiongol.com) Received: from smtp02.dentaku.gol.com (smtp02.dentaku.gol.com [203.216.5.72]) by mx1.freebsd.org (Postfix) with ESMTP id E665F13C4C1 for ; Thu, 8 Nov 2007 10:22:25 +0000 (UTC) (envelope-from n-butcher=freebsd-current=freebsd.org=sbibybnr@fusiongol.com) Received: from pat.gol.co.jp ([203.216.1.191] helo=[127.0.0.1]) by smtp02.dentaku.gol.com with esmtpa (Dentaku) id 1Iq4Ob-0003Ul-NN for ; Thu, 08 Nov 2007 19:13:57 +0900 Message-ID: <4732E165.1020502@fusiongol.com> Date: Thu, 08 Nov 2007 19:13:57 +0900 From: Nathan Butcher User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: freebsd-current@freebsd.org X-Enigmail-Version: 0.95.5 Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV GOL X-Abuse-Complaints: abuse@gol.com Subject: ZFS -> samba directory quirk X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Nov 2007 10:22:30 -0000 I'm not sure if I'm the only one seeing this, but I have a ZFS-samba set up between my FreeBSD7-BETA2 test machine and a Windows XP box. The samba install is from ports and is the latest version (it is patched for zfs I believe). On occasion I will find that directory information sometimes goes funky when coming out on the Windows XP side. On one occasion, files that *should* have been in the directory didn't show up in Windows, and on one occasion, a filename for a particular file appeared *twice* (and deleting it deleted both instances!). A refresh of the directory in Windows seemed to fix this quirk temporarily. Of course, everything looks normal on the FreeBSD ZFS side, so I'm inclined to point the finger at samba doing something weird with ZFS.