From owner-freebsd-fs@FreeBSD.ORG Mon Jan 30 04:30:16 2012 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 F3A22106564A for ; Mon, 30 Jan 2012 04:30:15 +0000 (UTC) (envelope-from feld@feld.me) Received: from mwi1.coffeenet.org (unknown [IPv6:2607:f4e0:100:300::2]) by mx1.freebsd.org (Postfix) with ESMTP id BB6B28FC0C for ; Mon, 30 Jan 2012 04:30:15 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=feld.me; s=blargle; h=Message-Id:From:Mime-Version:Date:Subject:To:Content-Type; bh=wsm0H9dx6i+QnkW7OzFsce1LvC5O7mDeS0UXOMFCbWM=; b=bu7WxRT3xw6Tw86lnnakztmVD39xx/Ac87iqzLV6PFdcw9fyEty4Vc0xAGjq//1wnvP4XpEhtXUAgG1oShuWt5+XX14d4YoskJqwiDRDaISov6PlnWqSkKJtgXdGuC5h; Received: from localhost ([127.0.0.1] helo=mwi1.coffeenet.org) by mwi1.coffeenet.org with esmtp (Exim 4.77 (FreeBSD)) (envelope-from ) id 1Rrisg-000NpI-BI for freebsd-fs@freebsd.org; Sun, 29 Jan 2012 22:30:15 -0600 Received: from feld@feld.me by mwi1.coffeenet.org (Archiveopteryx 3.1.4) with esmtpsa id 1327897808-18602-18600/5/3; Mon, 30 Jan 2012 04:30:08 +0000 Content-Type: text/plain; charset=iso-8859-15; format=flowed; delsp=yes To: freebsd-fs@freebsd.org Date: Sun, 29 Jan 2012 22:30:06 -0600 Mime-Version: 1.0 From: Mark Felder Message-Id: User-Agent: Opera Mail/11.60 (Win32) X-SA-Score: -1.0 Subject: ZFS sync / ZIL clarification 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: Mon, 30 Jan 2012 04:30:16 -0000 I believe I was told something misleading a few weeks ago and I'd like to have this officially clarified. NFS on ZFS is horrible unless you have sync = disabled. I was told this was effectively disabling the ZIL, which is of course naughty. Now I stumbled upon this tonight: > Just for the archives... sync=disabled won't disable disable the zil, > it'll disable waiting for a disk-flush on fsync etc. With a battery > backed controller cache, those flushes should go to cache, and bepretty > mich free. You end up tossing away something for nothing. Is this accurate?