From owner-freebsd-questions@FreeBSD.ORG Thu Sep 22 13:14:11 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8AD7116A41F for ; Thu, 22 Sep 2005 13:14:11 +0000 (GMT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from mail28.sea5.speakeasy.net (mail28.sea5.speakeasy.net [69.17.117.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5CC5943D58 for ; Thu, 22 Sep 2005 13:13:56 +0000 (GMT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: (qmail 17893 invoked from network); 22 Sep 2005 13:13:54 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail28.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 22 Sep 2005 13:13:54 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id 7A55149; Thu, 22 Sep 2005 09:13:53 -0400 (EDT) Sender: lowell@be-well.ilk.org To: snacktime References: <1f060c4c0509211854c712a8@mail.gmail.com> <1f060c4c0509211907214639c0@mail.gmail.com> From: Lowell Gilbert Date: 22 Sep 2005 09:13:52 -0400 In-Reply-To: <1f060c4c0509211907214639c0@mail.gmail.com> Message-ID: <44slvxb5yn.fsf@be-well.ilk.org> Lines: 11 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-questions@freebsd.org Subject: Re: Freebsd 5.4 panic on ffs_blkfree: freeing free frag X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Sep 2005 13:14:11 -0000 snacktime writes: > This looks very similar, however it happened on 6.0. > > http://people.freebsd.org/~pho/stress/log/cons107.html Could be similar; can't be sure without full debugging information. It doesn't seem likely to be an on-disk problem offhand (fair warning; that is *very* offhand), but forcing a clean fsck is certainly a good idea just to be sure.