Hi,
At 1:16 pm -0700 3/10/99, Archie Cobbs wrote:
>I'd suggest turining off soft-updates first.[etc]
Here's a thing. I'd forgotten that I'd borrowed the scratch drive (where
/usr/obj is) out of this box a while back. It seems when I replaced it I
forgot to enable softupdates (which had been on p
Bob Bishop writes:
> >Unfortunatly with this sort of panic, the panic is correct. The actual
> >dammage was done some (possibly considerable) time before. So a traceback
> >isn't so useful.
>
> OK, so how do I proceed to get some more useful info? It's still happening.
I'd suggest turining off s
Hi,
At 1:13 pm -0700 2/10/99, Julian Elischer wrote:
>[...]
>Unfortunatly with this sort of panic, the panic is correct. The actual
>dammage was done some (possibly considerable) time before. So a traceback
>isn't so useful.
OK, so how do I proceed to get some more useful info? It's still happen
On Sat, 2 Oct 1999, Bob Bishop wrote:
> >
> >On Sat, 2 Oct 1999, Bob Bishop wrote:
> >
> >> Hi,
> >>
> >> panic: free vnode isn't
> >>
> >> with yesterday's kernel (cvsup Fri Oct 1 04:02:32 BST 1999), on an SMP
> >
got to mention that /usr/src is NFS (but it doesn't seem likely that's
relevant).
>julian
>
>
>On Sat, 2 Oct 1999, Bob Bishop wrote:
>
>> Hi,
>>
>> panic: free vnode isn't
>>
>> with yesterday's kernel (cvsup Fri Oct 1 04:02:32 BST 19
sft updates?
is it possible the filesystem got totally full?
(that combination prooduces a bug that kirk is looking at...)
julian
On Sat, 2 Oct 1999, Bob Bishop wrote:
> Hi,
>
> panic: free vnode isn't
>
> with yesterday's kernel (cvsup Fri Oct 1 04:02:32 BST
Hi,
panic: free vnode isn't
with yesterday's kernel (cvsup Fri Oct 1 04:02:32 BST 1999), on an SMP
system early on in buildworld.
Skeletal traceback (must get serial console fixed up):
panic
getnewvnode
ffs_vget
ufs_lookup
ufs_vnoperate
vfs_cache_lookup
ufs_vnoperate
lookup
na
