From owner-cvs-all@FreeBSD.ORG  Wed Jul 21 18:34:45 2004
Return-Path: <owner-cvs-all@FreeBSD.ORG>
Delivered-To: cvs-all@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 0549016A4CE; Wed, 21 Jul 2004 18:34:45 +0000 (GMT)
Received: from elvis.mu.org (elvis.mu.org [192.203.228.196])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id AD9B643D31; Wed, 21 Jul 2004 18:34:44 +0000 (GMT)
	(envelope-from bright@elvis.mu.org)
Received: by elvis.mu.org (Postfix, from userid 1192)
	id 747D75C8D0; Wed, 21 Jul 2004 11:34:44 -0700 (PDT)
Date: Wed, 21 Jul 2004 11:34:44 -0700
From: Alfred Perlstein <alfred@freebsd.org>
To: Scott Long <scottl@freebsd.org>
Message-ID: <20040721183444.GS95729@elvis.mu.org>
References: <200407211604.i6LG4kFK052991@repoman.freebsd.org>
	<40FE95FD.6000101@cronyx.ru> <40FE9A94.5090805@root.org>
	<40FE9FFF.6050702@freebsd.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <40FE9FFF.6050702@freebsd.org>
User-Agent: Mutt/1.4.2.1i
cc: src-committers@freebsd.org
cc: cvs-src@freebsd.org
cc: cvs-all@freebsd.org
cc: Roman Kurakin <rik@cronyx.ru>
cc: Robert Watson <rwatson@freebsd.org>
cc: Nate Lawson <nate@root.org>
Subject: Re: cvs commit: src/sys/kern kern_shutdown.c
X-BeenThere: cvs-all@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: CVS commit messages for the entire tree <cvs-all.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/cvs-all>,
	<mailto:cvs-all-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/cvs-all>
List-Post: <mailto:cvs-all@freebsd.org>
List-Help: <mailto:cvs-all-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/cvs-all>,
	<mailto:cvs-all-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Jul 2004 18:34:45 -0000

* Scott Long <scottl@freebsd.org> [040721 09:57] wrote:
> 
> It should be noted that syncing on panic is almost never a good idea.
> The whole idea of panic() is to signal that the system has gotten into
> an inconsistent and unrecoverable state.  Do you really want to trust it
> to spam your drive with buffers that are in an unknown state via a set
> of codepaths that are in an unknown state?  It's much better to just
> step back and let fsck try to repair the damage.  I can't remember a
> single time in the last 4 years when a panic actually successfuly synced
> out all of the buffers and shutdown the filesystem, so it's not likely
> that you'll avoid a fsck on reboot with this.

It's not about avoiding a fsck, it's about recovering the last 30+ seconds
of disk activity.  Ie, files you've just created and such.

-- 
- Alfred Perlstein
- Research Engineering Development Inc.
- email: bright@mu.org cell: 408-480-4684