From owner-freebsd-fs@FreeBSD.ORG  Wed Jan  9 15:22:24 2013
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by hub.freebsd.org (Postfix) with ESMTP id EFE14A23;
 Wed,  9 Jan 2013 15:22:24 +0000 (UTC)
 (envelope-from borjam@sarenet.es)
Received: from proxypop03b.sare.net (proxypop03b.sare.net [194.30.0.251])
 by mx1.freebsd.org (Postfix) with ESMTP id B0F0F802;
 Wed,  9 Jan 2013 15:22:24 +0000 (UTC)
Received: from [172.16.2.2] (izaro.sarenet.es [192.148.167.11])
 by proxypop03.sare.net (Postfix) with ESMTPSA id 560C79DD64F;
 Wed,  9 Jan 2013 16:15:33 +0100 (CET)
Subject: Re: rc.d script for memory based zfs intent log
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Borja Marcos <borjam@sarenet.es>
In-Reply-To: <20130109023327.GA1888@FreeBSD.org>
Date: Wed, 9 Jan 2013 16:15:38 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <AAEA3C3D-7FD5-4F26-A73B-47264F05E088@sarenet.es>
References: <20130109023327.GA1888@FreeBSD.org>
To: John <jwd@FreeBSD.org>
X-Mailer: Apple Mail (2.1085)
Cc: FreeBSD Filesystems <freebsd-fs@freebsd.org>
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Jan 2013 15:22:25 -0000


On Jan 9, 2013, at 3:33 AM, John wrote:

> Hi Folks,
>=20
>   Here's an rc.d script that provides a nice performance boost on
> ZFS/NFS based file servers. It also helps in other areas not specific
> to NFS.
>=20
>   It attaches the log device at system startup and removes it at
> system shutdown time. Example;

In case of a crash, seems to be riskier than using sync=3Ddisabled on =
the datasets you need.  What is the impact on the data integrity of a =
suddenly disappearing ZIL?






Borja.