From owner-freebsd-scsi Wed Oct 14 16:01:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA13766 for freebsd-scsi-outgoing; Wed, 14 Oct 1998 16:01:42 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA13761; Wed, 14 Oct 1998 16:01:40 -0700 (PDT) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.7/8.8.5) with ESMTP id RAA06139; Wed, 14 Oct 1998 17:01:12 -0600 (MDT) Message-Id: <199810142301.RAA06139@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Terry Lambert cc: gibbs@plutotech.com (Justin T. Gibbs), Don.Lewis@tsc.tdk.com, freebsd-fs@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: filesystem safety and SCSI disk write caching In-reply-to: Your message of "Wed, 14 Oct 1998 22:40:09 -0000." <199810142240.PAA01660@usr04.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 14 Oct 1998 16:54:22 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >I think the moral of this story is that you can't rely on UPS's, >and instead should only rely on single-state-transition based >finite state automatons if you need to be able to rely on anything. The moral of this story is that everyone should decide what kinds of performance/safety tradeoffs they are willing to make and design their systems accordingly. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message