From owner-freebsd-scsi Tue Oct 13 23:08:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA16596 for freebsd-scsi-outgoing; Tue, 13 Oct 1998 23:08:58 -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 XAA16591; Tue, 13 Oct 1998 23:08:56 -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 AAA16953; Wed, 14 Oct 1998 00:08:38 -0600 (MDT) Message-Id: <199810140608.AAA16953@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Don Lewis cc: "Justin T. Gibbs" , Terry Lambert , freebsd-fs@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: filesystem safety and SCSI disk write caching In-reply-to: Your message of "Tue, 13 Oct 1998 22:59:24 PDT." <199810140559.WAA17612@salsa.gv.tsc.tdk.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 14 Oct 1998 00:01:53 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >} The drive will reinitialize to the 'power on state' if the power fluctuates >} into a zone that might invalidate it's run-time state. It doesn't take a >} very long spike for the drive's power-glitch sensor to go off. In this >} case, dropping cached contents on the floor is much safer than attempting >} to continue from an unknown state. > >If that's the reason for the problem that I saw, then the UPS the >system was plugged into wasn't sufficient to prevent the problem. Why is that? Do you have gremlins walking around hitting the reset buttons on your machines? The UPS should isolate the machine from any drop in power that would cause it to lose its brain other than that caused by a hardware failure or an administrator hitting the reset or power switch. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message