Date: Wed, 24 Sep 1997 15:24:19 -0500 From: Chris Csanady <ccsanady@bob.scl.ameslab.gov> To: Brandon Gillespie <brandon@roguetrader.com> Cc: Wilko Bulte <wilko@yedi.iaf.nl>, tlambert@primenet.com, freebsd-fs@FreeBSD.ORG Subject: Re: Known problems with async ufs? Message-ID: <199709242024.PAA06819@bob.scl.ameslab.gov> In-Reply-To: Your message of "Wed, 24 Sep 1997 13:56:11 MDT." <Pine.BSF.3.96.970924135516.6508A-100000@roguetrader.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>On Wed, 24 Sep 1997, Wilko Bulte wrote: > >> As Brandon Gillespie wrote... >> > On Wed, 24 Sep 1997, Terry Lambert wrote: >> > > That answer the question? >> > >> > Very much so, thanks! >> > >> > Basically, with all of the down-play towards using an async FS it seemed >> > as if there may be bugs within the actual async code, and not just the >> > crash/power-fail situation problems. >> > >> > I personally am running off a smart-ups, and have a daemon monitoring it >> > so it will shutdown properly, if need be. >> >> UPS don't buy you much if the machine crashes/panics on it's own. Lets >> say due to a memory parity error, or hard I/O error in swap or something. >> >> My point is: it's not only power fails that can hurt you. > >hrm, true > >Ok... what (if any) plans are there to make async at least as ''stable'' >as ext2fs? I'm under the impression that ext2fs does something so it can >recover from "bad things" better.. It's more or less as stable, but they just brainwash their users into thinking that it is safe. In fact my friend recently had his entire fs trashed. Oh well.. Hopefully, this will not be an issue for long considering Kirk's soft updates work. Chris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199709242024.PAA06819>