Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 21 Jan 2012 14:36:23 -0800
From:      Freddie Cash <fjwcash@gmail.com>
To:        Alexander Leidinger <Alexander@leidinger.net>
Cc:        fs@freebsd.org
Subject:   Re: Question about ZFS with log and cache on SSD with GPT
Message-ID:  <CAOjFWZ58odQZC9ud__RPBJGahtrZpYXk4ZnoZQv5%2B3qXN1NbZA@mail.gmail.com>
In-Reply-To: <20120121230616.00006267@unknown>
References:  <4F193D90.9020703@digiware.nl> <20120121162906.0000518c@unknown> <4F1B0177.8080909@digiware.nl> <20120121230616.00006267@unknown>

next in thread | previous in thread | raw e-mail | index | archive | help
On Jan 21, 2012 2:06 PM, "Alexander Leidinger" <Alexander@leidinger.net>
wrote:
>
> On Sat, 21 Jan 2012 19:18:31 +0100 Willem Jan Withagen
> <wjw@digiware.nl> wrote:

> > Our are you more concerned out losing the the LOG en thus possible
> > losing data.
>
> Yes. If one piece of the involved hardware dies, you lose data.

To clarify this a bit.  You will only lose data is:
  - data is written to ZIL device
  - entire system crashes before the data in the ZIL is written to disk
  - ZIL device is not available at pool import time

If you write data to the ZIL, then the system crashes *but all data in ZIL
is already written to the pool*, and the ZIL device is not available at
pool import time, then no data is lost, and the pool import will continue
without the separate ZIL.

ZFS pools prior to ZFSv19 could not cope with a missing ZIL device at pool
import time, so those pools were effectively lost. The only way to recover
data was through some finicky zdb stuff. Thus, you had to use a mirrored
log device to mitigate this risk.

Since ZFSv19,  though, a pool can be imported with a faulted ZIL device,
and carry on. Only data that's only in the ZIL, not written to the pool, is
lost.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOjFWZ58odQZC9ud__RPBJGahtrZpYXk4ZnoZQv5%2B3qXN1NbZA>