Panic in a vkernel: getblk: vnode 0x669232e8 has no object!
rumcic at gmail.com
Fri Apr 4 01:24:13 PDT 2008
Content-Type: text/plain; charset=us-ascii
X-Trace: 1207297454 crater_reader.dragonflybsd.org 871 126.96.36.199
Xref: crater_reader.dragonflybsd.org dragonfly.bugs:8272
Matthew Dillon wrote:
> :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.
Er ... now that is a very good question ... I don't remember right now if I did
ever fill it up, but the base image which I copy (and abuse the copy) is very
old, so there is a possibility of that ... oh well, guess it's time to remake
the base image.
More information about the Bugs