Panic in a vkernel: getblk: vnode 0x669232e8 has no object!
dillon at apollo.backplane.com
Fri Apr 4 00:20:49 PDT 2008
:Alrighty ... I triggered another panic (while checking out the pkgsrc tree ...
:but it seems to me a different panic unrelated to this?
:Checkout latest pkgsrc-current...
:mode = 030721, inum = 64, fs =
:panic: ffs_valloc: dup alloc
:Trace beginning at frame 0x6565480c
That's a different, unrealted panic.
Did you at any time prior to the checkout fill up the filesystem?
There's a bug in UFS that can cause corruption when the filesystem
fills up which we haven't patched yet.
More information about the Bugs