From owner-cvs-all Mon Oct 12 13:00:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA27998 for cvs-all-outgoing; Mon, 12 Oct 1998 13:00:15 -0700 (PDT) (envelope-from owner-cvs-all@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 NAA27981; Mon, 12 Oct 1998 13:00:09 -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 NAA03712; Mon, 12 Oct 1998 13:59:45 -0600 (MDT) Message-Id: <199810121959.NAA03712@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith cc: Kenneth Merry , cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/sys/cam/scsi scsi_da.c In-reply-to: Your message of "Mon, 12 Oct 1998 11:09:54 PDT." <199810121809.LAA07119@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 12 Oct 1998 13:53:00 -0600 From: "Justin T. Gibbs" Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk > >I think what this is telling us is that attempting to use anything other >than the least common denominator as the default is a Bad Idea. > If a device has an enabled write cache and you don't perform a synchronize cache on shutdown, the user may corrupt their file systems when powering off the system. The number of drives that fail to respond to a synchronize cache command is far, far smaller than the number of drives shipped with new systems that have write cache enabled and require the use of this command in order to guarantee safe shutdown. To not use the command would encourage a tech support nightmare. I'm certainly open to suggestions on how to limit the chances of the synchronize cache command causing problems. Perhaps we should only do this if WCE is turned on in the cache control page. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message