From owner-freebsd-hackers Tue Dec 16 07:59:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA04629 for hackers-outgoing; Tue, 16 Dec 1997 07:59:17 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from server.local.sunyit.edu (A-T34.rh.sunyit.edu [150.156.210.241]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA04261 for ; Tue, 16 Dec 1997 07:54:01 -0800 (PST) (envelope-from perlsta@cs.sunyit.edu) Received: from localhost (perlsta@localhost) by server.local.sunyit.edu (8.8.8/8.8.5) with SMTP id KAA13718; Tue, 16 Dec 1997 10:57:30 -0500 (EST) X-Authentication-Warning: server.local.sunyit.edu: perlsta owned process doing -bs Date: Tue, 16 Dec 1997 10:57:29 -0500 (EST) From: Alfred Perlstein X-Sender: perlsta@server.local.sunyit.edu To: Igor Timkin cc: Terry Lambert , freebsd-hackers@FreeBSD.ORG Subject: Re: panic: blkfree: freeling free block/frag In-Reply-To: <199712161442.RAA24936@crocus.gamma.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk if possible try new ram/cache, or maybe motherboard.... check your heat situation... On Tue, 16 Dec 1997, Igor Timkin wrote: > Terry Lambert writes: > > > Every 4-8 days my news server (~10 full incoming feeds, ~50 > > > outgoing feeds) crash: > > > panic: blkfree: freeing free block > > > or > > > panic: blkfree: freeing free frag > > > > Long Answer: > > > > Generally, this type of problem means you should rebuild the news spool, > > since *any* corruption could result in invalid information on the disk > > that could result in a panic. > > > > Most likely, you crashed once, and you expected fsck to do something > > that it can't do reliably: recover an async mounted partition. The > > partition was "recovered" and marked clean, but when you reference > > a particular disk metadata construct, it goes off into the weeds > > because the recovery was imperfect. > > Unfortunally, I still have this problem. > I had make newfs 5 days ago. But yestarday I got the same panic > (uptime 5.2 days): > > ivt@news:/var/tmp/innfeed:2:306>gdb -k /sys/compile/NEWS/kernel /usr/local/news/crash/vmcore.1 > GDB is free software and you are welcome to distribute copies of it > under certain conditions; type "show copying" to see the conditions. > There is absolutely no warranty for GDB; type "show warranty" for details. > GDB 4.16 (i386-unknown-freebsd), > Copyright 1996 Free Software Foundation, Inc... > IdlePTD 1f0000 > current pcb at 1d79c0 > panic: blkfree: freeing free block > #0 boot (howto=256) at ../../kern/kern_shutdown.c:266 > 266 dumppcb.pcb_cr3 = rcr3(); > (kgdb) where > #0 boot (howto=256) at ../../kern/kern_shutdown.c:266 > #1 0xe01105e2 in panic (fmt=0xe0188a85 "blkfree: freeing free block") > at ../../kern/kern_shutdown.c:390 > #2 0xe0188c57 in ffs_blkfree (ip=0xe3e50500, bno=10, size=4096) > at ../../ufs/ffs/ffs_alloc.c:1230 > #3 0xe018b09a in ffs_indirtrunc (ip=0xe3e50500, lbn=-12, dbn=394248, > lastbn=-1, level=0, countp=0xdfbffd9c) at ../../ufs/ffs/ffs_inode.c:500 > #4 0xe018aac8 in ffs_truncate (ap=0xdfbffe74) at ../../ufs/ffs/ffs_inode.c:317 > #5 0xe018e6a5 in ufs_inactive (ap=0xdfbffea0) at vnode_if.h:1003 > #6 0xe012fb3f in vrele (vp=0xe3b12800) at vnode_if.h:699 > #7 0xe012fa33 in vput (vp=0xe3b12800) at ../../kern/vfs_subr.c:858 > #8 0xe0191e80 in ufs_remove (ap=0xdfbffef4) at ../../ufs/ufs/ufs_vnops.c:697 > #9 0xe0131d25 in unlink (p=0xe4dc6e00, uap=0xdfbfff94, retval=0xdfbfff84) > at vnode_if.h:459 > #10 0xe01ac1ff in syscall (frame={tf_es = 39, tf_ds = -541130713, tf_edi = 1, > tf_esi = 28736, tf_ebp = -541074456, tf_isp = -541065244, > tf_ebx = 28944, tf_edx = 0, tf_ecx = 41472, tf_eax = 10, tf_trapno = 7, > tf_err = 7, tf_eip = 268950145, tf_cs = 31, tf_eflags = 582, > tf_esp = -541074568, tf_ss = 39}) at ../../i386/i386/trap.c:890 > #11 0x1007da81 in ?? () > #12 0x2453 in ?? () > #13 0x2914 in ?? () > #14 0x1095 in ?? () > > fsck -y /var/spool/news: > ** /dev/rccd0c > ** Phase 1 - Check Blocks and Sizes > INCORRECT BLOCK COUNT I=12450 (152 should be 0) > CORRECT? yes > > ** Phase 2 - Check Pathnames > UNALLOCATED I=12447 OWNER=news MODE=0 > SIZE=0 MTIME=Dec 15 21:35 1997 > NAME=/relcom/netnews/big/11105 > > REMOVE? yes > > UNALLOCATED I=12448 OWNER=news MODE=0 > SIZE=0 MTIME=Dec 15 21:35 1997 > NAME=/relcom/netnews/big/11107 > > REMOVE? yes > > UNALLOCATED I=12449 OWNER=news MODE=0 > SIZE=0 MTIME=Dec 15 21:35 1997 > NAME=/relcom/nennews/big/11108 > > REMOVE? yes > > ** Phase 3 - Check Connectivity > ** Phase 4 - Check Reference Counts > LINK COUNT FILE I=12450 OWNER=news MODE=100664 > SIZE=0 MTIME=Dec 15 21:35 1997 COUNT 0 SHOULD BE 1 > ADJUST? yes > > ** Phase 5 - Check Cyl groups > FREE BLK COUNT(S) WRONG IN SUPERBLOCK > SALVAGE? yes > > BLK(S) MISSING IN BIT MAPS > SALVAGE? yes > > SUMMARY INFORMATION BAD > SALVAGE? yes > > CLEAN FLAG NOT SET IN SUPERBLOCK > FIX? yes > > I don't have any ahc and kernel error and warning messages, > the clean news spool. > > I have crash dump image and may put it on my ftp server or download > it on any server (512M). >