Re: My current box still got panic after ATAng

It seems Shin-ichi Yoshimoto wrote:
> My recent kernel still got the panic when I tried to do CVSup.
> 
> # cvsup -g -z -L 2 /home/yosimoto/mk/daemon-supfile 2>&1 | tee /var/tmp/log/cvsup.`date "+%m%d.%H.%M.%S"`;
> Parsing supfile "/home/yosimoto/mk/daemon-supfile"
> Connecting to cvsup.jp.FreeBSD.org
> Connected to cvsup.jp.FreeBSD.org
> Server software version: SNAP_16_1f
> Negotiating file attribute support
> Exchanging collection information
> Establishing multiplexed-mode data connection
> Running
> ata2: spurious interrupt - status=0x50 error=0x00 reason=0x00
> Updating collection cvs-all/cvs
>  Append to CVSROOT-ports/commitlogs/ports
> /home: bad dir ino 7843753 at offset 0: mangled entry
> panic: ufs_dirbad: bad dir
> cpuid = 0; lapic.id = 00000000
> Debugger("panic")
> Stopped at      Debugger+0x4f:  xchgl   %ebx,in_Debugger.0
> db> t
> Debugger(c0367b19,0,c03717da,e786f9cc,100) at Debugger+0x4f
> panic(c03717da,c64454b0,77afa9,0,c0371794) at panic+0x153
> ufs_dirbad(c72d49d8,0,c0371794,0,e786fa48) at ufs_dirbad+0x53
> ufs_lookup(e786fb08,e786fb44,c0247f48,e786fb08,e786fc3c) at ufs_lookup+0x416
> ufs_vnoperate(e786fb08,e786fc3c,e786fc50,0,c648fe40) at ufs_vnoperate+0x18
> vfs_cache_lookup(e786fb88,e786fba4,c024cf5f,e786fb88,c648fe40) at vfs_cache_lookup+0x2d8
> ufs_vnoperate(e786fb88,c648fe40,0,c648fe40,c648fe40) at ufs_vnoperate+0x18
> lookup(e786fc28,c67ee800,400,e786fc44,c648fe40) at lookup+0x2e0
> namei(e786fc28,81d8ac4,60,0,c648fe40) at namei+0x208
> lstat(c648fe40,e786fd14,8,0,2) at lstat+0x52
> syscall(bfbf002f,bfbf002f,81d002f,bfbffab8,bfbffad4) at syscall+0x289
> Xint0x80_syscall() at Xint0x80_syscall+0x1d
> --- syscall (190, FreeBSD ELF32, lstat), eip = 0x28192507, esp = 0x81d89c0, ebp = 0x81d8a5c ---

Hmm, have you run fsck on that filesystem lately ?

-Søren