Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

panic: bad dir with recent -current

Since updating a machine from sources of around 201110270000Z (and again
about 24 hours later), said machine panics with the following traceback
(recovered from dmesg):

wsdisplay0: screen 4 added (80x25, vt100 emulation)
wsdisplay0: screen 5 added (80x25, vt100 emulation)
/: bad dir ino 434153 at offset 0: mangled entry
panic: bad dir
cpu1: Begin traceback...
printf_nolog(c063daba,cd0bb2f8,69fe9,0,0,c05f95f1,1,d0ecc0c0,200,d0ecc0c0) at 
 at netbsd:ufs_dirbadentry
 at netbsd:ufs_lookup+0x3fc
 at netbsd:VOP_LOOKUP+0x33
at netbsd:lookup_once+0x19b
namei_tryemulroot(0,1,0,8,1,c065edf4,ce2bfcf4,c0543d50,bb90801c,cdfb8800) at 
namei(ce2bfbb0,ce2bfbf0,2000,4752c9,cec2a100,ce07c180,ce2bfbf0,0,ce07c19c,0) at 
do_sys_stat(bb90801c,40,ce2bfc18,0,a,cec2a0c0,ce2bfc9c,ce2bfc3c,1,5430a) at 
 at netbsd:sys___stat50+0x2a
 at netbsd:syscall+0xa4
cpu1: End traceback...

dumping to dev 0,1 offset 133223
dump Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
    2006, 2007, 2008, 2009, 2010, 2011
    The NetBSD Foundation, Inc.  All rights reserved.

although there appears to be a core dump recovered by savecore, gdb
complains that it is an unrecognized format.

Just prior to the panic recovered above, I rebooted in single-user mode
and forced a full filesystem check on all filesystems.  The root file
system (as indicated in the panic message) had accumulated a number of
unreferenced files.

Surveying the files indicated that they had no business being on the
root filesystem at all, but were files that should have been on another
local filesystem (which passed its fsck).  The panic was prompted by
attempting to build ".../pkgsrc/multimedia/gnash" from pkgsrc-HEAD.
An earlier panic (from the night before) was prompted by the nightly
maintenance script.

So, it seems to behave as if the mounted filesystem becomes detached
and writes start happening on the "parent" filesystem...  All filesystems
are mounted with the "log" option and fsck always pronounces them "already
clean", even after the panic reboot.

(Given the time at which I'm composing this, the machine has just
now fallen over again due to the nightly maintenance activity.)

It's going to take at least one more panic to find which directory
has the inode complained about.  I'm guessing its the one on which
is the mount point for the filesystem in question.

|/"\ John D. Baker, KN5UKS               NetBSD     Darwin/MacOS X
|\ / jdbaker[snail]mylinuxisp[flyspeck]com    OpenBSD            FreeBSD
| X  No HTML/proprietary data in email.   BSD just sits there and works!
|/ \ GPGkeyID:  D703 4A7E 479F 63F8 D3F4  BD99 9572 8F23 E4AD 1645

Home | Main Index | Thread Index | Old Index