From owner-freebsd-scsi Sun Oct 18 16:08:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA18004 for freebsd-scsi-outgoing; Sun, 18 Oct 1998 16:08:54 -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 QAA17999; Sun, 18 Oct 1998 16:08:53 -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 RAA21386; Sun, 18 Oct 1998 17:08:21 -0600 (MDT) Message-Id: <199810182308.RAA21386@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Terry Lambert cc: julian@whistle.com (Julian Elischer), guido@gvr.org, dkelly@hiwaay.net, freebsd-fs@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: filesystem safety and SCSI disk write caching In-reply-to: Your message of "Sun, 18 Oct 1998 19:28:58 -0000." <199810181928.MAA19832@usr06.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 18 Oct 1998 17:01:30 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Perhaps they realized that the mpst likely event after a power >fluctuation was a bus reset, and figured "why bother?". And why is this relevant? The only reasons allowed for cache contents never making it to the disk are power loss and hardware failure. A bus reset (assuming the hard reset alternative is in effect) only clears any transactions that have not been reported as completed to the host. Perhaps you should add the SCSI II and SCSI II specs to your list of things to read. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message