From owner-freebsd-stable Thu Nov 21 16:35:43 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA00447 for stable-outgoing; Thu, 21 Nov 1996 16:35:43 -0800 (PST) Received: from mail.webspan.net (mail.webspan.net [206.154.70.7]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA00441; Thu, 21 Nov 1996 16:35:37 -0800 (PST) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (8.7.5/8.7.3) with ESMTP id TAA01048; Thu, 21 Nov 1996 19:33:26 -0500 (EST) Received: from orion.webspan.net (localhost [127.0.0.1]) by orion.webspan.net (8.7.5/8.7.3) with ESMTP id TAA21459; Thu, 21 Nov 1996 19:33:26 -0500 (EST) Message-Id: <199611220033.TAA21459@orion.webspan.net> To: Thomas David Rivers cc: freebsd-stable@freefall.freebsd.org, freebsd-hackers@freefall.freebsd.org From: "Gary Palmer" Subject: Re: panic: ffs_valloc: dup alloc In-reply-to: Your message of "Sat, 16 Nov 1996 07:53:24 EST." <199611161253.HAA26583@lakes.water.net> Date: Thu, 21 Nov 1996 19:33:26 -0500 Sender: owner-stable@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 :-( > 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? Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info