From owner-freebsd-stable@FreeBSD.ORG Sun Dec 5 09:16:31 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 21A3C16A4CE for ; Sun, 5 Dec 2004 09:16:31 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id EC1FB43D5D for ; Sun, 5 Dec 2004 09:16:30 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 7ED4151212; Sun, 5 Dec 2004 01:22:24 -0800 (PST) Date: Sun, 5 Dec 2004 01:22:24 -0800 From: Kris Kennaway To: wkwu@FreeBSD.csie.NCTU.edu.tw Message-ID: <20041205092224.GA39160@xor.obsecurity.org> References: <20041205090944.GA53819@FreeBSD.csie.NCTU.edu.tw> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="wac7ysb48OaltWcw" Content-Disposition: inline In-Reply-To: <20041205090944.GA53819@FreeBSD.csie.NCTU.edu.tw> User-Agent: Mutt/1.4.2.1i cc: FreeBSD-stable@freebsd.org Subject: Re: sync disk before panic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Dec 2004 09:16:31 -0000 --wac7ysb48OaltWcw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Dec 05, 2004 at 05:09:44PM +0800, wkwu@FreeBSD.csie.NCTU.edu.tw wro= te: > Our system needs several hours to fsck the disks after panic. >=20 > Is is possible to sync the disks before kernel panic? sysctl kern.sync_on_panic=3D1 Disabled by default because it's usually more trouble than it's worth (if your system is panicking, that means something has gone terribly wrong, and it may not be possible to sync without causing further damage). In real terms, this means that you'll likely get another panic when the kernel tries to sync when it panics, and this can obscure things like stack tracebacks and panic messages that are useful for tracking down the cause of the problem. Kris --wac7ysb48OaltWcw Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBstNQWry0BWjoQKURAtmAAJ9SHPhTxbXKY8H0506l3i13DlI4swCg7xnn 610iJta4df0epxOjQpRGlOg= =3YIM -----END PGP SIGNATURE----- --wac7ysb48OaltWcw--