From owner-freebsd-bugs@FreeBSD.ORG Wed Apr 18 04:30:07 2007 Return-Path: X-Original-To: freebsd-bugs@hub.freebsd.org Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C9A6816A403 for ; Wed, 18 Apr 2007 04:30:07 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 45BCB13C4BE for ; Wed, 18 Apr 2007 04:30:07 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l3I4U7KT041216 for ; Wed, 18 Apr 2007 04:30:07 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l3I4U78k041211; Wed, 18 Apr 2007 04:30:07 GMT (envelope-from gnats) Date: Wed, 18 Apr 2007 04:30:07 GMT Message-Id: <200704180430.l3I4U78k041211@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Kris Kennaway Cc: Subject: Re: kern/111766: "panic: ffs_blkfree: freeing free block" during disk activity X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Kris Kennaway List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Apr 2007 04:30:07 -0000 The following reply was made to PR kern/111766; it has been noted by GNATS. From: Kris Kennaway To: Rong-En Fan Cc: Kris Kennaway , FreeBSD-gnats-submit@FreeBSD.org Subject: Re: kern/111766: "panic: ffs_blkfree: freeing free block" during disk activity Date: Wed, 18 Apr 2007 00:22:07 -0400 --vtzGhvizbBRQ85DL Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Apr 18, 2007 at 12:14:35PM +0800, Rong-En Fan wrote: > On Wed, Apr 18, 2007 at 12:06:15AM -0400, Kris Kennaway wrote: > > On Wed, Apr 18, 2007 at 12:01:53PM +0800, Rong-En Fan wrote: > > > I think I tried once but in vain. Some previous backtrace > > > at http://www.rafan.org/FreeBSD/panic/freeing_free_block/ > > > I haven't see this since last Oct, but the filesystem does not > > > get full recently (we got larger disks). > >=20 > > Unfortunately I dont think the backtrace is very useful, it's > > reporting damage that occured at some earlier time. > >=20 > > > >From previous experience, usually the panic is triggered on > > > the full partition but I saw once or twice that it's triggered > > > on another non-full filesystem. >=20 > Let me clear it a bit. When it's triggered on non-full filesystem, > I have another filesystem is full and some clients trying to write > to the full one. >=20 > > I am not entirely sure whether it is really due to a full filesystem, > > because I've also come across it in random circumstances. I have also > > spent some time stressing full filesystems without causing the panic. > > If you can come up with a way to reliably produce it, that would be > > very useful (possibly essential). >=20 > Perhaps in the summer, I can find some free time to do this. > Just curious, have you tried exported the filesystem and stress > via nfs client? I didn't try that, but will give it a shot. Kris --vtzGhvizbBRQ85DL Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFGJZzvWry0BWjoQKURAkTLAKDN2qSiC2JzjhJP9nJbeB4TnOkhBgCfV6YG XMBK0NuGFBdah4qlN8i++bQ= =vfMW -----END PGP SIGNATURE----- --vtzGhvizbBRQ85DL--