From owner-freebsd-current@FreeBSD.ORG Sun Oct 7 10:37:15 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 79DCB16A41A for ; Sun, 7 Oct 2007 10:37:15 +0000 (UTC) (envelope-from se@FreeBSD.org) Received: from spacemail1-out.mgmt.space.net (spacemail1-out.mgmt.Space.Net [194.97.149.146]) by mx1.freebsd.org (Postfix) with ESMTP id 11AE413C4A5 for ; Sun, 7 Oct 2007 10:37:14 +0000 (UTC) (envelope-from se@FreeBSD.org) X-SpaceNet-SBRS: None X-IronPort-AV: E=Sophos;i="4.21,240,1188770400"; d="scan'208";a="66379727" Received: from mail.atsec.com ([195.30.252.105]) by spacemail1-out.mgmt.space.net with ESMTP; 07 Oct 2007 12:37:12 +0200 Received: from [192.168.0.12] (p5087739D.dip.t-dialin.net [80.135.115.157]) (Authenticated sender: se@atsec.com) by mail.atsec.com (Postfix) with ESMTP id 2723B720932; Sun, 7 Oct 2007 12:37:10 +0200 (CEST) Message-ID: <4708B6D0.3090009@FreeBSD.org> Date: Sun, 07 Oct 2007 12:37:04 +0200 From: Stefan Esser User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: =?UTF-8?B?RGFnLUVybGluZyBTbcO4cmdyYXY=?= References: <4707569E.6010400@freebsd.org> <868x6gpk3i.fsf@ds4.des.no> <47083883.6000503@freebsd.org> <863awn9uoe.fsf@ds4.des.no> In-Reply-To: <863awn9uoe.fsf@ds4.des.no> X-Enigmail-Version: 0.95.3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: Darren Reed , FreeBSD Current , pjd@FreeBSD.org Subject: Re: ZFS & NFS integration... 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: Sun, 07 Oct 2007 10:37:15 -0000 Dag-Erling Smørgrav wrote: > Darren Reed writes: >> Dag-Erling Smørgrav wrote: >>> Darren Reed writes: >>>> Whats the planned status for ZFS+NFS with 7.0? >>> Don't Do It, basically. >> This sounds like a "shoot yourself in the foot" comment. >> >> Why? > > I haven't figured out the exact details yet, but apparently when the > client closes a file that was opened read / write, the server stops > responding to that client. I've been operating a file server (P3/733, 512MB) that way for many months. Besides the problems with Samba on ZFS (one of the clients is a DVB-T receiver that reads/writes to SMB shares) there have never been problems. Other clients use NFS (and there exists an unsupported hack that makes the DVB-T receiver use NFS instead of SMB, which I installed to work around the Samba issue, which means that this client now also uses NFS). I use another machine to cut and clean recordings and while the P3 only has an fxp adapter (i.e. 100baseTX), I often max out this link for significant durations (hours at a time). The server seems to run as long as I let it (at least months, since I have upgraded it a few times since ZFS went into the tree). Since my applications/uses include R/W access to files via NFS, I can say that it at least can work reliably. That does not mean, that there can not be problems with NFS to ZFS based files, but there are real world uses that just work. In my case, there is little concurrent access to the NFS server (occasionally I record one or two video streams and watch a third one over the DVB-T box or another client, but there are hardly ever more than two NFS clients at a time). ZFS as a whole has rough edges (especially since the auto-tuning of kernel parameters does not account for it, yet). Regards, STefan