From owner-freebsd-bugs@FreeBSD.ORG Fri Jun 4 08:11:46 2010 Return-Path: Delivered-To: freebsd-bugs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CB939106567A for ; Fri, 4 Jun 2010 08:11:46 +0000 (UTC) (envelope-from pcc@gmx.net) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id 1B7798FC2B for ; Fri, 4 Jun 2010 08:11:45 +0000 (UTC) Received: (qmail 32594 invoked by uid 0); 4 Jun 2010 07:45:04 -0000 Received: from 84.163.244.195 by www151.gmx.net with HTTP; Fri, 04 Jun 2010 09:45:00 +0200 (CEST) Content-Type: text/plain; charset="utf-8" Date: Fri, 04 Jun 2010 09:45:00 +0200 From: "Peter Cornelius" In-Reply-To: <201006030800.o53802PX037019@freefall.freebsd.org> Message-ID: <20100604074500.211900@gmx.net> MIME-Version: 1.0 References: <201006030800.o53802PX037019@freefall.freebsd.org> To: FreeBSD-gnats-submit@FreeBSD.org, freebsd-bugs@FreeBSD.org X-Authenticated: #491680 X-Flags: 0001 X-Mailer: WWW-Mail 6100 (Global Message Exchange) X-Priority: 5 X-Provags-ID: V01U2FsdGVkX1+0nrB+C/C0Or66wao/J0Pz2p9apZmMvms2KJsKp8 ASp27cPXB55otUqQW8wLWPPyesHxeBaxZLhw== Content-Transfer-Encoding: 8bit X-GMX-UID: mspgAf0zbHIhIdK4PjQ0QPsiJihyalBM X-FuHaFi: 0.54000000000000004 Cc: Subject: Re: kern/147420: [nfs] kldload nfs modules causes nfs-aware kernel panic after a while X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jun 2010 08:11:46 -0000 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