what happens to pool if ZIL dies on ZFS v14

David Brodbeck gull at gull.us
Tue Sep 21 22:38:24 UTC 2010


On Fri, Sep 17, 2010 at 9:18 AM, Jeremy Chadwick
<freebsd at jdc.parodius.com> wrote:
> Given the severity of this predicament, then why is it people are
> disabling the ZIL (via vfs.zfs.zil_disable=1) ?

If you don't have a separate log device, synchronous writes are very
slow with the ZIL enabled.  This isn't such a big deal unless you're
using NFS, where essentially every write is synchronous.  Then many
common operations become conspicuously slow, especially compared to
Linux, which isn't as fastidious about requiring data to be flushed
all the way to the platters before signaling to NFS clients that the
operation is complete.

The danger in this case isn't that the pool could be damaged, but that
a server crash could result in data not being written to disk even
though the client believes the operation completed successfully;
essentially, this would be silent data loss, since NFS server reboots
are supposed to be invisible to client applications.


More information about the freebsd-fs mailing list