From owner-freebsd-fs@FreeBSD.ORG Fri Sep 17 17:03:56 2010 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 308801065694 for ; Fri, 17 Sep 2010 17:03:56 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-ey0-f182.google.com (mail-ey0-f182.google.com [209.85.215.182]) by mx1.freebsd.org (Postfix) with ESMTP id B0FA28FC0A for ; Fri, 17 Sep 2010 17:03:55 +0000 (UTC) Received: by eyx24 with SMTP id 24so1353014eyx.13 for ; Fri, 17 Sep 2010 10:03:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=Ar8Gn3h8buZ8O1b58Ev77hHwGRPDy85BVSfVVna5yB4=; b=DnyMP0xJLY0uusxTJz/b/5h7O8eGD3au4kJH6DY9CfgXgBXtU6OHRqinwxYNnArwlZ z42/aOEGqSDme+T5NqTlsWCmOzHu5cL61uzCL9TDgD3rIM2kLsjFz4AqNS0Og2fwa+EC UcuvGb1a619iYOh+XKAI1dLFlwlw0Au3wLoYo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=uONXS2DEwYYnXiY3HGiLMShnnq06Kx++OtxM1EaqLQ0zxDFiNHQQ/EXGbaxErDrXNf n1Xups1i8l7EskLyw7wkZcRRxPGMqfTNIbE+c5qpYSn4hsbDFE+vrkK+IL/a/4kg2oUn QHpm6FweTa55fOiV6CEjEArEd6xcGmtSEx3zY= MIME-Version: 1.0 Received: by 10.223.124.70 with SMTP id t6mr42020far.80.1284743034350; Fri, 17 Sep 2010 10:03:54 -0700 (PDT) Received: by 10.223.110.197 with HTTP; Fri, 17 Sep 2010 10:03:54 -0700 (PDT) In-Reply-To: <20100917163732.GA59537@icarus.home.lan> References: <4C9385B0.2080909@shatow.net> <20100917161847.GA58503@icarus.home.lan> <20100917163732.GA59537@icarus.home.lan> Date: Fri, 17 Sep 2010 10:03:54 -0700 Message-ID: From: Freddie Cash To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: what happens to pool if ZIL dies on ZFS v14 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: Fri, 17 Sep 2010 17:03:56 -0000 On Fri, Sep 17, 2010 at 9:37 AM, Jeremy Chadwick wrote: > I was under the impression ZFS still managed to utilise the ZIL when a > pool didn't have any "log" devices associated with it (possibly some > sort of statically-allocated amount of RAM?) Yes, there has been a ZIL in ZFS from the very beginning. Originally, it was part of the pool. Then the ability to have separate log (slog) devices was added. At the time that slog support was added, the recommendation was to mirror the slogs, since losing the slog would kill the entire pool. Then in ZFSv19, support for removing slogs and booting with a dead slog was added, so one could run with non-mirrored slogs. Disabling the ZIL has no bearing on whether or not the pool dies when the slog dies. > You can search the FreeBSD lists for people continually advocating > vfs.zfs.zil_disable=3D1. =C2=A0There's even a couple blog posts from engi= neers > talking about how the only way to get their filers to behave decently > was to disable the ZIL[1][2][3]. =C2=A0In most (every?) cases I've seen w= here > someone advocates disabling the ZIL, pool details aren't provided, which > leads me to believe their pools have no "log" devices. Correct. However, disabling the ZIL is orthogonal to having slog devices and whether or not the pool dies when the slog dies. You can have separate log devices, then disable the ZIL, but the slog devices will remain as part of the pool, just unused. For example, in ZFSv14, if you have a separate log device, then disable the ZIL, then the slog device dies (or you physically remove it), and you reboot ... your pool is dead as the log device is inaccessible. (There may be rare occasions when you may be able to boot without the slog if there's no data in the slog, but I wouldn't count on it.) > Here's a better way to phrase my question: does vfs.zfs.zil_disable=3D1 d= o > anything if there aren't any "log" devices in use (in any pool)? Yes, it disables the in-pool ZIL. ZFS always has a ZIL unless you disable it. the only difference is where the ZIL is located (in-pool or on separate device). --=20 Freddie Cash fjwcash@gmail.com