From owner-freebsd-current Fri Jan 24 23: 4: 5 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B951537B401; Fri, 24 Jan 2003 23:04:04 -0800 (PST) Received: from HAL9000.homeunix.com (12-233-57-224.client.attbi.com [12.233.57.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B82443EB2; Fri, 24 Jan 2003 23:04:00 -0800 (PST) (envelope-from dschultz@uclink.Berkeley.EDU) Received: from HAL9000.homeunix.com (localhost [127.0.0.1]) by HAL9000.homeunix.com (8.12.6/8.12.5) with ESMTP id h0P73r0A001318; Fri, 24 Jan 2003 23:03:53 -0800 (PST) (envelope-from dschultz@uclink.Berkeley.EDU) Received: (from das@localhost) by HAL9000.homeunix.com (8.12.6/8.12.5/Submit) id h0P73qHa001317; Fri, 24 Jan 2003 23:03:52 -0800 (PST) (envelope-from dschultz@uclink.Berkeley.EDU) Date: Fri, 24 Jan 2003 23:03:52 -0800 From: David Schultz To: Greg Lehey Cc: Andy Farkas , Thomas David Rivers , Robert Watson , current@FreeBSD.ORG Subject: Re: I've just had a massive file system crash Message-ID: <20030125070352.GA933@HAL9000.homeunix.com> Mail-Followup-To: Greg Lehey , Andy Farkas , Thomas David Rivers , Robert Watson , current@FreeBSD.ORG References: <20030124093754.GD2402@sydney.worldwide.lemis.com> <20030124093754.GD2402@sydney.worldwide.lemis.com> <200301241153.h0OBrf654388@lakes.dignus.com> <20030124093754.GD2402@sydney.worldwide.lemis.com> <20030124203116.H62832-100000@hewey.af.speednet.com.au> <20030125043817.GD929@sydney.worldwide.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030125043817.GD929@sydney.worldwide.lemis.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thus spake Greg Lehey : > I've been thinking about what happened, and I have a possibility: the > session before shutdown included a lot of writing to that file system, > and I did a shutdown -p. It's possible that the shutdown powered off > the system before the disk had flushed its cache. For the moment I'm > avoiding shutdown -p, but when I get home I'll try to provoke it > again. FreeBSD's ``fix'' for this problem is the same as Windows 98's. Specifically, there is a 5-second delay (tuneable: kern.shutdown.poweroff_delay) after all buffers are flushed but before the power is cut. Maybe we ought to be sending FLUSH CACHE commands to all drives and waiting for them to finish. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message