Re: [PANIC] ufs_dirbad: bad dir

This message from doug white might apply:
http://lists.freebsd.org/pipermail/freebsd-current/2004-November/042704.html

On Fri, 9 Sep 2005, David O'Brien wrote:

> Anyone own this one?  Happened during a kernel build.
> The running kernel was:
>     _at_(#)FreeBSD 7.0-CURRENT #526: Sun Aug 21 15:56:54 PDT 2005
>
> --
> -- David  (obrien_at_FreeBSD.org)
>
> GNU gdb 20040810 [GDB v6.x for FreeBSD]
> ---
> panic: ufs_dirbad: bad dir
> cpuid = 1
> KDB: stack backtrace:
> kdb_backtrace(c06b586e,1,c06ad17c,f09257d0,c4e8cd80) at 0xc052cdae = kdb_backtrace+0x2e
> panic(c06ad17c,c4e71200,7396a,170,c06ad136) at 0xc050fe38 = panic+0x128
> ufs_dirbad(c52519cc,170,c06ad136,0,f0925844) at 0xc060797d = ufs_dirbad+0x4d
> ufs_lookup(f09258f0,c565bbb0,f0925bec,c565bbb0,f092592c) at 0xc06070fd = ufs_lookup+0x3ad
> VOP_CACHEDLOOKUP_APV(c06dd920,f09258f0,f0925bec,c4e8cd80,c5b6ee80) at 0xc067b25e = VOP_CACHEDLOOKUP_APV+0x9e
> vfs_cache_lookup(f0925998,f0925998,c565bbb0,c565bbb0,0) at 0xc056768a = vfs_cache_lookup+0xca
> VOP_LOOKUP_APV(c06dd920,f0925998,c4e8cd80,c5648c2c,0) at 0xc067b176 = VOP_LOOKUP_APV+0xa6
> lookup(f0925bc4,0,c06a2cb2,b4,1a4) at 0xc056c27e = lookup+0x44e
> namei(f0925bc4,0,c06a33bd,846,c565bbb0) at 0xc056bb3f = namei+0x41f
> vn_open_cred(f0925bc4,f0925cc4,180,c5b6ee80,5) at 0xc057fece = vn_open_cred+0x2ae
> vn_open(f0925bc4,f0925cc4,180,5,1) at 0xc057fc13 = vn_open+0x33
> kern_open(c4e8cd80,80768e0,0,1,1b6) at 0xc0578158 = kern_open+0xc8
> open(c4e8cd80,f0925d04,c,422,3) at 0xc0578056 = open+0x36
> syscall(3b,3b,3b,4,282cd210) at 0xc0670622 = syscall+0x2e2
> Xint0x80_syscall() at 0xc065c31f = Xint0x80_syscall+0x1f
> --- syscall (5, FreeBSD ELF32, open), eip = 0x2829e6c7, esp = 0xbfbfe0dc, ebp = 0xbfbfe108 ---
> Uptime: 22m49s
> _______________________________________________
> freebsd-current_at_freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"
>