On Thu, Jul 26, 2007 at 03:42:31PM +0200, Pawel Jakub Dawidek wrote: > Let me explain what disabling ZIL really means. Once ZIL is disabled, > fsync(2) is a no-op, ie. calling fsync(2) on a descriptor doesn't mean > your data would be safely stored on disk at the time function returns. > There is no data corruption for local use, only this fsync(2) problem. > > "Data corruption" can happen from NFS client point of view, when your > ZFS file system is exported over NFS and your NFS server crashes. Does this increase the window after an fsync is performed that a crash or power loss will lose recent changes? That's what I got from reading the descriptions of ZIL, perhaps "corruption" was a poor choice of words. CraigReceived on Thu Jul 26 2007 - 12:01:14 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:15 UTC