From owner-freebsd-current@FreeBSD.ORG Mon Jun 5 14:21:52 2006 Return-Path: X-Original-To: current@freebsd.org 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 21C0C16B635 for ; Mon, 5 Jun 2006 14:21:47 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 13BD543D88 for ; Mon, 5 Jun 2006 14:21:32 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 356701A4D80; Mon, 5 Jun 2006 07:21:31 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 363E8512A6; Mon, 5 Jun 2006 10:21:28 -0400 (EDT) Date: Mon, 5 Jun 2006 10:21:28 -0400 From: Kris Kennaway To: "Bjoern A. Zeeb" Message-ID: <20060605142128.GB66078@xor.obsecurity.org> References: <20060605114900.M79180@maildrop.int.zabbadoz.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="0ntfKIWw70PvrIHh" Content-Disposition: inline In-Reply-To: <20060605114900.M79180@maildrop.int.zabbadoz.net> User-Agent: Mutt/1.4.2.1i Cc: FreeBSD current mailing list Subject: Re: panic: ffs_freefile: freeing free inode X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Jun 2006 14:22:05 -0000 --0ntfKIWw70PvrIHh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jun 05, 2006 at 11:51:12AM +0000, Bjoern A. Zeeb wrote: > Hi, >=20 > this is with a kernel from late May (I'll have to check when I had > synced the sources once I get it booting again...). > The machine crashed with a new kernel with the next boot I got: >=20 > ... > properly dismounted i.e. you previously panicked and then ran bg fsck? This can cause further panics until you force a fg fsck, since your filesystem had damage that was not safe to run with. Just say no to bg fsck! Kris --0ntfKIWw70PvrIHh Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEhD3nWry0BWjoQKURAj+TAKCb4eHEW7xSxt+tepMjfiyb84DfvgCeKz1k RB8TFg4moW4EhaVHDkojOpE= =cgar -----END PGP SIGNATURE----- --0ntfKIWw70PvrIHh--