Date: Thu, 12 May 2011 09:08:05 -0500 (CDT) From: Bob Friesenhahn <bfriesen@simple.dallas.tx.us> To: Jeremy Chadwick <freebsd@jdc.parodius.com> Cc: freebsd-fs@freebsd.org Subject: Re: ZFS: How to enable cache and logs. Message-ID: <alpine.GSO.2.01.1105120902220.20825@freddy.simplesystems.org> In-Reply-To: <20110512083429.GA58841@icarus.home.lan> References: <4DCA5620.1030203@dannysplace.net> <4DCB455C.4020805@dannysplace.net> <alpine.GSO.2.01.1105112146500.20825@freddy.simplesystems.org> <20110512033626.GA52047@icarus.home.lan> <4DCB7F22.4060008@digsys.bg> <20110512083429.GA58841@icarus.home.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 12 May 2011, Jeremy Chadwick wrote: > > What guarantee is there that the intent log -- which is written to the > disk -- actually got written to the disk in the middle of a power > failure? There's a lot of focus there on the idea that "the intent log > will fix everything, but may lose writes", but what guarantee do I have > that the intent log isn't corrupt or botched during a power failure? This is pretty easy. Zfs requests that the disk containing the intent log commit its update (and waits for completion) before it returns from the "write" request. As long as the disk does not lie, the data will be present after the reboot. Note that many SSDs do lie about cache commit requests and these are best avoided for anything to do with zfs. Bob -- Bob Friesenhahn bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.GSO.2.01.1105120902220.20825>