rc.d script for memory based zfs intent log

[Johan Hendriks]

Artem Belevich schreef:
> On Wed, Jan 9, 2013 at 7:15 AM, Borja Marcos <borjam at sarenet.es> wrote:
>> In case of a crash, seems to be riskier than using sync=disabled on the datasets you need.  What is the impact on the data integrity of a suddenly disappearing ZIL?
> Losing ZIL used to be fatal for the pool.
> I think in recent ZFS versions (v28?) you will only lose transactions
> that were not committed to the pool yet, but don't quote me on that.
> _______________________________________________
> freebsd-fs at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-fs
> To unsubscribe, send any mail to "freebsd-fs-unsubscribe at freebsd.org"
Loosing the ZIL will loose data written to the ZIL not jet flushed to 
the pool itself.
So most likely you will have corrupted data.
So for a ZIL use a mirror pair!
You can add and remove a ZIL from the pool without problem from version 
28 and above.

Same thing goes if you have sync=disabled.
Data acknowledge by the server but not flushed to the pool will end up 
in corrupt data.
Disabeling sync is something you do not want to do.
If you need, use the ZIL.

regards
Johan Hendriks
Neuteboom Automatisering