Date: Mon, 10 Sep 2007 17:07:51 -0500 From: Craig Boston <cb@severious.net> To: Peter Schuller <peter.schuller@infidyne.com> Cc: freebsd-fs@freebsd.org Subject: Re: UFS not handling errors correctly Message-ID: <20070910220751.GC10142@nowhere> In-Reply-To: <20070909221142.GA6435@hyperion.scode.org> References: <46E4225F.1020806@gmx.net> <46E42D14.5060605@FreeBSD.org> <20070909200933.GA98161@hyperion.scode.org> <46E45E54.6040207@FreeBSD.org> <20070909221142.GA6435@hyperion.scode.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Sep 10, 2007 at 12:11:42AM +0200, Peter Schuller wrote: > Kris Kenneway said: > > Unfortunately there are many ways in which this can fail, mostly involving > > external factors violating the assumptions upon which soft updates relies. > > For example, the data written on disk may not correspond to the data > > dispatched by soft updates, due to things like write caching in the > > hardware, write reordering, data corruption, unpredictable disk behaviour > > during power loss, hardware failure, etc. > > I am aware of this too (and paranoid about it). Although it's still branded experimental for now, you may want to look at ZFS after the 7.0 release. There's a whole host of things to consider (different performance characteristics, possible patent problems, etc), but it's one of the most paranoid filesystems I've seen. It doesn't really trust that the disk actually works correctly and goes to great lengths to recover from read failure or random data corruption. It still sometimes panics on write failure, but that may be considered a feature. Craig
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070910220751.GC10142>