From owner-freebsd-current@FreeBSD.ORG Fri Jun 1 13:41:19 2007 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 97E1816A400 for ; Fri, 1 Jun 2007 13:41:19 +0000 (UTC) (envelope-from se@FreeBSD.org) Received: from frueh.atsec.com (frueh.atsec.com [217.110.13.170]) by mx1.freebsd.org (Postfix) with ESMTP id 12F8813C44C for ; Fri, 1 Jun 2007 13:41:18 +0000 (UTC) (envelope-from se@FreeBSD.org) Received: from [10.2.2.88] (se-pad.koeln.atsec [10.2.2.88]) by frueh.atsec.com (omb_smtp 1.5.8) with ESMTP; Fri, 01 Jun 2007 16:27:24 +0200 (CEST) Message-ID: <46601E44.0@FreeBSD.org> Date: Fri, 01 Jun 2007 15:25:24 +0200 From: Stefan Esser User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: Johan Hendriks References: <57200BF94E69E54880C9BB1AF714BBCB011170@w2003s01.double-l.local> <20070531214611.GA19588@Gatekeeper.FreeBSD.org> <57200BF94E69E54880C9BB1AF714BBCB19BADA@w2003s01.double-l.local> In-Reply-To: <57200BF94E69E54880C9BB1AF714BBCB19BADA@w2003s01.double-l.local> X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Cc: freebsd-current@FreeBSD.org Subject: Re: Samba access to ZFS broken 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: Fri, 01 Jun 2007 13:41:20 -0000 Johan Hendriks wrote: > > -----Oorspronkelijk bericht----- > Van: Stefan Eßer [mailto:se@FreeBSD.org] > Verzonden: donderdag 31 mei 2007 23:46 > Aan: Johan Hendriks > CC: freebsd-current@FreeBSD.org > Onderwerp: Samba access to ZFS broken > >> On 2007-05-31 14:18 +0200, Johan Hendriks wrote: > >> I don't think so, since I'm observing the same problem on a >> single-CPU system with different configuration. Common is >> Samba access to files stored on ZFS. > >> My current work around is to NFS export the file systems and to >> mount them on localhost. Samba works just fine when configured >> to access files in ZFS via this NFS loopback. (It does not work >> on a nullfs mount of the ZFS partitions.) > >> I have no time for further tests before the weekend, but this >> seems to either be a bug introduced by a recent ZFS change, or >> to be caused by compilation with gcc-4.2. > >> Regards, Stefan > > Ok nice to hear it is not me. Well, what finally saved me after hours of effort spent trying to get samba to work was your mail, which described exactly the symptoms my system showed. When I read that it was specific to ZFS, I tried with an MFS exported via samba, which just worked ... I had spent hours recompiling all dependencies and looking at a possible config file error. So, thank you for reporting it and for mentioning ZFS ;-) > It used to work, and if I recall it did not work with version 3.0.24 also after the gcc update. Ok, I've got a small file server running -current (because I wanted to give ZFS a try) and I needed to reboot to disable ZFS read-ahead (which appears to be a pessimisation at least on small servers; I think vfs.zfs.prefetch_disable="1" should be the default, it seems to not be adaptive as in our UFS, where read-ahead is gradually increased if a file is really sequentially read). > But I did not have time to go look for the problem at that moment. I plan to test the previous kernel (from early may) with the current samba (and if that does not work, the previous samba with the new kernel). But the local-NFS work-around keeps my system working despite the current samba/ZFS incompatibility. (I can't easily move the data to UFS and need to provide CIFS access to a large spool area for an appliance that supports just that protocol ...) Regards, STefan