Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 22 Nov 1996 09:31:37 -0500 (EST)
From:      Thomas David Rivers <ponds!rivers@dg-rtp.dg.com>
To:        ponds!freebsd.org!gpalmer, ponds!lakes.water.net!rivers
Cc:        ponds!freefall.freebsd.org!freebsd-hackers, ponds!freefall.freebsd.org!freebsd-stable
Subject:   Re: panic: ffs_valloc: dup alloc
Message-ID:  <199611221431.JAA11106@lakes.water.net>

next in thread | raw e-mail | index | archive | help
> 
> 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 -




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199611221431.JAA11106>