Date: Wed, 21 Jul 2004 11:34:44 -0700 From: Alfred Perlstein <alfred@freebsd.org> To: Scott Long <scottl@freebsd.org> Cc: Nate Lawson <nate@root.org> Subject: Re: cvs commit: src/sys/kern kern_shutdown.c Message-ID: <20040721183444.GS95729@elvis.mu.org> In-Reply-To: <40FE9FFF.6050702@freebsd.org> References: <200407211604.i6LG4kFK052991@repoman.freebsd.org> <40FE95FD.6000101@cronyx.ru> <40FE9A94.5090805@root.org> <40FE9FFF.6050702@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
* 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040721183444.GS95729>