From owner-freebsd-hackers Fri Nov 22 09:21:23 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA02823 for hackers-outgoing; Fri, 22 Nov 1996 09:21:23 -0800 (PST) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA02773 for ; Fri, 22 Nov 1996 09:20:42 -0800 (PST) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA28177; Fri, 22 Nov 1996 12:20:03 -0500 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Fri, 22 Nov 1996 12:20 EST Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.7.5/8.7.3) with ESMTP id JAA04008; Fri, 22 Nov 1996 09:29:38 -0500 (EST) Received: (from rivers@localhost) by lakes.water.net (8.7.5/8.6.9) id JAA11106; Fri, 22 Nov 1996 09:31:37 -0500 (EST) Date: Fri, 22 Nov 1996 09:31:37 -0500 (EST) From: Thomas David Rivers Message-Id: <199611221431.JAA11106@lakes.water.net> To: ponds!freebsd.org!gpalmer, ponds!lakes.water.net!rivers Subject: Re: panic: ffs_valloc: dup alloc Cc: ponds!freefall.freebsd.org!freebsd-hackers, ponds!freefall.freebsd.org!freebsd-stable Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Thomas David Rivers wrote in message ID > <199611161253.HAA26583@lakes.water.net>: > > > root@mail:/var/crash> gdb -k kernel vmcore.2 > > > 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.13 (i386-unknown-freebsd), > > > Copyright 1994 Free Software Foundation, Inc... > > > IdlePTD 1d5000 > > > current pcb at 1abd64 > > > panic: ffs_valloc: dup alloc > > > #0 boot (howto=260) at ../../i386/i386/machdep.c:912 > > > 912 } else { > > > (kgdb) bt > > > Welcome to the club :-) > > > This is the panic that I have had for several months, which is > > duplicated almost every night. > > Well, it just bit me again :-( The panic happens for me almost nightly. > > > Rest assured that several people are investigating this at this > > time... > > > I believe it has something to do with the inode allocation bits in > > ffs_valloc(). Others believe some race conditions in vnode allocation > > are to blaim, etc... David Greene is investigating other avenues. > > > It seems to me that we are closing in on the issue, if only by > > eliminating everything else :-) > > Question: > > it's always the same FS with me that bites the dust. Perhaps a > previous crash of the machine caused a FS corruption fsck isn't > picking up on. Has anyone who is being bothered by this dumped the fs > with *tar* (not dump) and resored to see if that fixes the problem? I completely reinstalled everything (wiped the disk, even did a low-level SCSI format) - the problem always resurfaced. Although, it didn't show up again for maybe two or three days. - Dave Rivers -