From owner-freebsd-fs@FreeBSD.ORG  Fri Mar 28 21:19:29 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 1602BFA4
 for <freebsd-fs@freebsd.org>; Fri, 28 Mar 2014 21:19:29 +0000 (UTC)
Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 8D382377
 for <freebsd-fs@freebsd.org>; Fri, 28 Mar 2014 21:19:28 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by woozle.rinet.ru (8.14.5/8.14.5) with ESMTP id s2SLJQT4047936;
 Sat, 29 Mar 2014 01:19:26 +0400 (MSK) (envelope-from marck@rinet.ru)
Date: Sat, 29 Mar 2014 01:19:26 +0400 (MSK)
From: Dmitry Morozovsky <marck@rinet.ru>
To: Freddie Cash <fjwcash@gmail.com>
Subject: Re: zfs l2arc warmup
In-Reply-To: <CAOjFWZ7h5080+zEvSfzxgENwP+PXEXKPXdEDHAtbx5RAxxWT0g@mail.gmail.com>
Message-ID: <alpine.BSF.2.00.1403290116550.60856@woozle.rinet.ru>
References: <CAFfb-hpi20062+HCrSVhey1hVk9TAcOZAWgHSAP93RSov3sx4A@mail.gmail.com>
 <CALfReydi_29L5tVe1P-aiFnm_0T4JJt72Z1zKouuj8cjHLKhnw@mail.gmail.com>
 <CAFfb-hpZos5-d3xo8snU1aVER5u=dSFRx-B-oqjFRTkT83w0Kg@mail.gmail.com>
 <20140328005911.GA30665@neutralgood.org>
 <CAFfb-hr=wR6nxqL+4tn-y2eQEw4n_g7rZoK9rRLnm_Ldcm1TZQ@mail.gmail.com>
 <alpine.BSF.2.00.1403290032070.60856@woozle.rinet.ru>
 <CAOjFWZ7h5080+zEvSfzxgENwP+PXEXKPXdEDHAtbx5RAxxWT0g@mail.gmail.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
X-NCC-RegID: ru.rinet
X-OpenPGP-Key-ID: 6B691B03
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3
 (woozle.rinet.ru [0.0.0.0]); Sat, 29 Mar 2014 01:19:26 +0400 (MSK)
Cc: "freebsd-fs@freebsd.org" <freebsd-fs@freebsd.org>
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.17
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: Fri, 28 Mar 2014 21:19:29 -0000

On Fri, 28 Mar 2014, Freddie Cash wrote:

[snip most again]

> Around ZFSv14-ish, the ability to import a pool with a missing ZIL was
> added.
> 
> Remember the flow of data in ZFS:
>   async write request --> TXG --> disk
>   sync write request --> ZIL
>                \--> TXG --> disk
> 
> All sync writes are written to the pool as part of a normal async TXG after
> its written sync to the ZIL.  And the ZIL is only ever read during pool
> import.

On the other side, doesn't it put the risk on sync-dependent, like database, 
systems? 

I'm thinking not about losing the transaction, but possibly putting your 
filesystem in the middle of (database PoV) transaction, hence render your DB 
inconsistent?

Quick googling seems to be uncertain about it...

-- 
Sincerely,
D.Marck                                     [DM5020, MCK-RIPE, DM3-RIPN]
[ FreeBSD committer:                                 marck@FreeBSD.org ]
------------------------------------------------------------------------
*** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru ***
------------------------------------------------------------------------