From owner-freebsd-current@FreeBSD.ORG Fri May 2 15:22:03 2003 Return-Path: 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 722C637B401; Fri, 2 May 2003 15:22:03 -0700 (PDT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA42243FB1; Fri, 2 May 2003 15:22:02 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.12.9/8.12.9) with SMTP id h42MMF9S084700; Fri, 2 May 2003 18:22:16 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Fri, 2 May 2003 18:22:15 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: current@FreeBSD.org In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: jeff@FreeBSD.org cc: kirk@mckusick.com Subject: Re: ffs_blkfree: freeing free block -- ps, traces, fsck log X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Fri, 02 May 2003 22:22:03 -0000 On Fri, 2 May 2003, Robert Watson wrote: > I updated a pxe box to a recent -current, and applied it to a UFS > partition I had on disk. I ran several parallel tars, an rm -Rf on one > of the tar extract targets, and a dd if=/dev/zero of=tmp on the > partition, and within a few minutes reproduced the nefarious > ffs_blkfree() panic. Some debugging information as follows; I included > stack traces of some of the more interesting threads. I've also > included the fsck output below -- the background file system checker was > not active at the time as it's manually mounted and fscked when used; I > believe the file system has never actually had the background file > system checker used on it, certainly not with a recent kernel. The > output from fsck -y on the partition is also attached. As you can see, > there are some alarming "ALLOCATED FRAG xxx MARKED FREE" messages. Actually, not so alarming -- I misinterpretted that as "allocated flag *was found* marked as free" rather than "hi, I'm fsck, and these frags that looked allocated in the free list were actually not used, so I marked them as free". The truncated inode message is the one that's actually bad :-). Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories