Date: Fri, 04 Jun 2010 09:45:00 +0200 From: "Peter Cornelius" <pcc@gmx.net> To: FreeBSD-gnats-submit@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: kern/147420: [nfs] kldload nfs modules causes nfs-aware kernel panic after a while Message-ID: <20100604074500.211900@gmx.net> In-Reply-To: <201006030800.o53802PX037019@freefall.freebsd.org> References: <201006030800.o53802PX037019@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Re. The situation has re-occurred at the exact same spot. panic: ufs_dirbad: /usr: bad dir ino 46895494 at offset 114368: mangled entry cpuid=1 KDB: enter: panic [thread pid 42063 tid 100153] Stopped at kdb_enter+0x3a movl $0,kdb_why I now googled with [nfs|ufs]_dirbad as a better keyword and hence now think that this issue actually may be a duplicate of kern/135690. I have a screenshot photo of a bt and can supply that on request; no textual dumps due to no dumps, sorry. I can leave the box on for another one or two hours if anyone wishes other commands meanwhile. What remains is the question how to find and get rid of the entry now, and whether I should go back to INVARIANTS* on in the kernel in order to avoid further mangling. The box previously has survived months up building (and running) RELENG_8 kernels & worlds happily during the last year with INVARIANTS on. Thanks, Peter. -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100604074500.211900>