From owner-freebsd-hackers Thu May 1 04:20:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA18082 for hackers-outgoing; Thu, 1 May 1997 04:20:40 -0700 (PDT) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id EAA18077 for ; Thu, 1 May 1997 04:20:36 -0700 (PDT) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA14315; Thu, 1 May 1997 07:20:04 -0400 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Thu, 1 May 1997 07:20 EDT Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.5/8.7.3) with ESMTP id GAA14257; Thu, 1 May 1997 06:43:34 -0400 (EDT) Received: (from rivers@localhost) by lakes.water.net (8.8.5/8.6.9) id GAA03818; Thu, 1 May 1997 06:50:14 -0400 (EDT) Date: Thu, 1 May 1997 06:50:14 -0400 (EDT) From: Thomas David Rivers Message-Id: <199705011050.GAA03818@lakes.water.net> To: ponds!freebsd.org!hackers, ponds!cdsnet.net!mrcpu Subject: Re: Panic's freeinf free block Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > FS panics make me extraordinarily nervous. (Running RELENG_2_2 supped a > couple of days ago). I'm not sure if I've related this to you; but this is amazingly similar to the daily panics I've reported for some time now. Also, I believe block number 22824 appears in my panics as well; it certainly looks familiar - but take that as a grain of salt. I have a rather reliable reproduction of this; but can't seem to make any headway on a fix... I know just a little less than I need to, and can't find the time to get over that hump :-) Just out of curiosity , you mentioned this was a different box from the one getting the NMIs before. Can you describe this box? - Dave Rivers - > > What is bno=22824 on line #2 down there? > > #0 boot (howto=256) at ../../kern/kern_shutdown.c:243 > #1 0xf010f1b2 in panic (fmt=0xf018ed7d "blkfree: freeing free block") > at ../../kern/kern_shutdown.c:367 > #2 0xf018ef4f in ffs_blkfree (ip=0xf1a85200, bno=22824, size=8192) > at ../../ufs/ffs/ffs_alloc.c:1230 > #3 0xf0190fce in ffs_truncate (ap=0xefbffdf8) at > ../../ufs/ffs/ffs_inode.c:343 > #4 0xf0194dd5 in ufs_inactive (ap=0xefbffe2c) at vnode_if.h:1003 > #5 0xf012e46f in vrele (vp=0xf19f6100) at vnode_if.h:699 > #6 0xf01a7c15 in vnode_pager_dealloc (object=0xf1c0e980) > at ../../vm/vnode_pager.c:203 > #7 0xf01a70fa in vm_pager_deallocate (object=0xf1c0e980) > at ../../vm/vm_pager.c:177 > #8 0xf01a2b14 in vm_object_terminate (object=0xf1c0e980) > at ../../vm/vm_object.c:416 > #9 0xf01a294f in vm_object_deallocate (object=0xf1c0e980) > at ../../vm/vm_object.c:353 > #10 0xf012e3ae in vrele (vp=0xf19f6100) at ../../kern/vfs_subr.c:881 > #11 0xf012e323 in vput (vp=0xf19f6100) at ../../kern/vfs_subr.c:858 > #12 0xf01982dc in ufs_remove (ap=0xefbffef8) at > ../../ufs/ufs/ufs_vnops.c:695 > #13 0xf01306ad in unlink (p=0xf1d22400, uap=0xefbfff94, retval=0xefbfff84) > at vnode_if.h:459 > #14 0xf01b53ff in syscall (frame={tf_es = 39, tf_ds = -272695257, > tf_edi = 33632, tf_esi = -272639072, tf_ebp = -272638720, > ---Type to continue, or q to quit--- > tf_isp = -272629788, tf_ebx = 1, tf_edx = -272640224, tf_ecx = 0, > tf_eax = 10, tf_trapno = 7, tf_err = 7, tf_eip = 268845169, tf_cs = > 31, > tf_eflags = 514, tf_esp = -272639116, tf_ss = 39}) > at ../../i386/i386/trap.c:890 > #15 0x10064071 in ?? () > #16 0x2c98 in ?? () > > > I'm running out of options, since it does it consistently. When you say consistent, how frequent do you mean? Are you running a news server, or some heavy-disk-hitter on this box? There is one real difference between your freeing-free-inode panics and mine (which I've reproduced on two machines) - I've never had mine happen as part of a VM operation... When I get this panic it is simply because I've unlinked a file... - Dave Rivers -