From owner-freebsd-current Sat Jan 23 14:03:34 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA22026 for freebsd-current-outgoing; Sat, 23 Jan 1999 14:03:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA22019 for ; Sat, 23 Jan 1999 14:03:33 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id NAA00373; Sat, 23 Jan 1999 13:55:48 -0800 (PST) Received: from s204m82.isp.whistle.com(207.76.204.82) via SMTP by alpo.whistle.com, id smtpdxDq364; Sat Jan 23 21:55:36 1999 Date: Sat, 23 Jan 1999 13:55:30 -0800 (PST) From: Julian Elischer X-Sender: julian@s204m82.isp.whistle.com To: "D. Rock" cc: current@FreeBSD.ORG Subject: Re: dirty fs after apm power off In-Reply-To: <199901232144.WAA10840@wurzelausix.cs.uni-sb.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG probably the drive needs write-caching turned off... On Sat, 23 Jan 1999, D. Rock wrote: > I have noticed this behaviour on at least one machine. > If I shutdown the machine with apm power off, the filesystem is dirty and > has to been checked on the next reboot. It seems, the power is cut too fast. > I don't have any problems with reboots. > It seems the drive doesn't have the time to write the superblock back to disk. > > I simply put a DELAY(4000000) in the apm_power_off() routine and the problem > fades away. > Any thoughts on doing this a configurable option? It doesn't break anything, > it only takes a few seconds longer for the machine to power off. > > The drive is a Maxtor Diamond Max (90432D2) 4GB IDE drive in an Asus SP98 > board. > > Daniel > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message