From owner-cvs-all Tue Dec 7 23:42: 6 1999 Delivered-To: cvs-all@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 41BBF15046; Tue, 7 Dec 1999 23:42:03 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.8.7/8.8.7) with ESMTP id XAA24692; Tue, 7 Dec 1999 23:43:27 -0800 Date: Tue, 7 Dec 1999 23:43:27 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Mike Smith Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/kern kern_shutdown.c In-Reply-To: <199912080738.XAA04106@mass.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk > > No- not quite. We should claim to support sane hardware, but shrug and > > hand the user the bullets if they want to end it all for themselves. > > Given that it's not hard to "support" this hardware in a functional > fashion, I think the effort is better than taking a bullet in the back > from our users. Feh. Coward. > > > > > (okay, so it's a couple of buffers at shutdown- in any case, perhaps the > > > > driver that sees Synchronize Cache not working should do something else- > > > > maybe calculate the Pareto for the first occurence of a y3k bug) > > > > > > You could just delay for a couple of seconds and guarantee that even if > > > the Synchronise Cache command didn't work, the drive will still have > > > flushed it's cache. Oops, looks like that's what I committed the other > > > day. > > > > You're toying with me, aren't you? > > Not at all. Since we can't guarantee a flush-to-stable-storage for > anything other than a subset of SCSI disks, the smart thing to do is to > wait for some time that ought to be greater than the typical flush delay > plus flush time between the last write we make and the time that we pull > the plug. A little empirical testing has suggested that about 5 seconds > works well here; this is enough to make most laptops power down cleanly > as opposed to leaving their disks dirty. *groan*.... I both agree and disagree. Look- if you have something broken wrt syncronize cache, the drive shouldn't be in buffered mode anyway. But if it's still broken no matter what, and the 5 second delay works (today), bravo (I guarantee you it will look very strange two years from now). (he waves his hands wildly, utters a curse, and leaves the conversation) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message