From owner-freebsd-current Tue Dec 17 15:24:55 2002 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 08AFF37B401 for ; Tue, 17 Dec 2002 15:24:54 -0800 (PST) Received: from beastie.mckusick.com (beastie.mckusick.com [209.31.233.184]) by mx1.FreeBSD.org (Postfix) with ESMTP id 95D6C43EC5 for ; Tue, 17 Dec 2002 15:24:53 -0800 (PST) (envelope-from mckusick@beastie.mckusick.com) Received: from beastie.mckusick.com (localhost [127.0.0.1]) by beastie.mckusick.com (8.12.3/8.12.3) with ESMTP id gBHNOl59018359; Tue, 17 Dec 2002 15:24:47 -0800 (PST) (envelope-from mckusick@beastie.mckusick.com) Message-Id: <200212172324.gBHNOl59018359@beastie.mckusick.com> To: Dan Nelson Subject: Re: panic: ffs_blkfree: freeing free block Cc: Aurelien Nephtali , current@FreeBSD.ORG In-Reply-To: Your message of "Mon, 16 Dec 2002 22:42:07 CST." <20021217044207.GA43444@dan.emsphone.com> Date: Tue, 17 Dec 2002 15:24:47 -0800 From: Kirk McKusick Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Date: Mon, 16 Dec 2002 22:42:07 -0600 > From: Dan Nelson > To: Aurelien Nephtali > Cc: current@FreeBSD.ORG > Subject: Re: panic: ffs_blkfree: freeing free block > > In the last episode (Dec 16), Aurelien Nephtali said: > > Hi, > > > > I got a panic today which occured during a background fsck, after a > > hard-reboot of the system. The dump from gdb is attached and I can, > > of course, provide more infos if needed. > > "Me too". My info attached as well; almost identical stack trace. > Kernel was built from sources cvsupped just after 2002/12/15 17:41:07 > PST. (Why in the heck are all the timestamps in commitlogs in PST??) > > -- > Dan Nelson > dnelson@allantgroup.com I introduced a bug to snapshots on 11/30/02 which did not get fixed until 12/15/02 which caused background fsck to (silently) fail to fix certain filesystem problems. If you ran background fsck on a system between 11/30 and 12/15 and then ran background fsck again on a system after that date, the earlier missed corruption causes the panic that you have seen. Once fixed on a post 12/15 system, it should not recur. You can avoid the panic by running `fsck -f -p' on all your system after upgrading to a post 12/15 system. If you find continued evidence of trouble after following the above procedures, please send me mail. Kirk McKusick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message