Date: Thu, 15 Oct 1998 01:10:37 -0700 (PDT) From: Julian Elischer <julian@whistle.com> To: "Justin T. Gibbs" <gibbs@plutotech.com> Cc: Studded <Studded@gorean.org>, freebsd-fs@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: filesystem safety and SCSI disk write caching Message-ID: <Pine.BSF.3.95.981015010606.5681B-100000@current1.whistle.com> In-Reply-To: <199810142254.QAA04647@pluto.plutotech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
The reason it comes up now is because the promise of soft updates to make a 'safer and faster filesystem' is threatenned by it. Inthe pas the 'sync' filesystem was known to have problem with crashes. and everybody just took that in their stride and didn't try find a reason for it. However with soft updates, there is a theoretical behaviour that is easy to understand and when a filesystem doesn't behae that way it become obvious.. the difference between 45 filesystem eros and 47 is not that great. The difference between 0 and 2 is much more noticeable, even though it's still only 2 errors. These problems have probably always occured. they were just not so obvious. On Wed, 14 Oct 1998, Justin T. Gibbs wrote: > > Which user community are you referring to? > > All of FreeBSD. > > >Has this write caching always been present, or was it introduced by CAM? > > It has always been present. > > -- > Justin > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95.981015010606.5681B-100000>