From owner-freebsd-stable Thu Jun 17 13: 8: 7 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ns1.aepnet.com (ns1.aepnet.com [208.129.247.1]) by hub.freebsd.org (Postfix) with ESMTP id A365F154E0 for ; Thu, 17 Jun 1999 13:08:05 -0700 (PDT) (envelope-from chris@ns1.aepnet.com) Received: from localhost (chris@localhost) by ns1.aepnet.com (8.8.7/8.8.7) with ESMTP id MAA16116; Thu, 17 Jun 1999 12:57:23 -0700 Date: Thu, 17 Jun 1999 12:57:23 -0700 (MST) From: chris To: Alfred Perlstein Cc: "Chad R. Larson" , Mike Smith , jedgar@fxp.org, sec@42.org, des@flood.ping.uio.no, freebsd-stable@FreeBSD.ORG Subject: Re: / not properly unmounted ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hehe, put the hard drives on their own separate power supply, and turn them off manually after the system powers itself down.. On Thu, 17 Jun 1999, Alfred Perlstein wrote: > On Thu, 17 Jun 1999, Chad R. Larson wrote: > > > As I recall, Mike Smith wrote: > > > > The first complaint was that the power-down was catching disk stuff > > > > still in cache. Setting an arbitrary delay on the way down seems > > > > inefficient at best, and possibly not sufficient. How about instead > > > > just making sure all buffers are flushed before the power-down is > > > > allowed to to occur, however long that takes? > > > > > > You can't do this, because it's the _disk_ that holds the cached data. > > > > Ok, I missed something in the original post? He's using some kind > > of caching (or RAID) controller? > > > > no, some drives have write caching, if you suddenly cut power, they > don't have enough charge left to write out the data in the cache. > > -Alfred > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message