From pcc@gmx.net  Sat Jun  5 11:11:21 2010
Return-Path: <pcc@gmx.net>
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id A275A106566B
	for <FreeBSD-gnats-submit@FreeBSD.org>; Sat,  5 Jun 2010 11:11:21 +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 E83FC8FC17
	for <FreeBSD-gnats-submit@FreeBSD.org>; Sat,  5 Jun 2010 11:11:20 +0000 (UTC)
Received: (qmail 1406 invoked by uid 0); 5 Jun 2010 11:11:19 -0000
Received: from 84.163.236.117 by www094.gmx.net with HTTP;
 Sat, 05 Jun 2010 13:11:18 +0200 (CEST)
Message-Id: <20100605111118.166660@gmx.net>
Date: Sat, 05 Jun 2010 13:11:18 +0200
From: "Peter Cornelius" <pcc@gmx.net>
To: FreeBSD-gnats-submit@FreeBSD.org
Cc: freebsd-bugs@FreeBSD.org
In-Reply-To: <20100604074500.211900@gmx.net>
Subject: ufs_dirbad, nullfs, jail (was: kern/147420: [nfs] kldload nfs modules
 causes nfs-aware kernel panic after a while)
References: <201006030800.o53802PX037019@freefall.freebsd.org>
 <20100604074500.211900@gmx.net>

>Number:         147496
>Category:       kern
>Synopsis:       ufs_dirbad, nullfs, jail (was: kern/147420: [nfs] kldload nfs modules causes nfs-aware kernel panic after a while)
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Jun 05 11:20:01 UTC 2010
>Closed-Date:    Thu Jun 10 00:43:18 UTC 2010
>Last-Modified:  Thu Jun 10 00:43:18 UTC 2010
>Originator:     
>Release:        
>Organization:
>Environment:
>Description:
 Hi,
 
 After two more failures, I now found the offending inode with find /usr -inum 46895494 and removed that directory with rm -rf <dir>.
 
 I re-enabled INVARIANTS, and I hope that the file system now at least is clean and that the server is stable now.
 
 As one point, I found the inode in a directory which usually is mounted for an (ez-) jail via nullfs. The jail is used to build packages and hence somewhat busy on file system level. I don't know whether this adds to the pointers of the issue.
 
 If the box is stable now, I would not pursue this matter further but am more than willing to answer questions.
 
 Thanks to all,
 
 Peter.
 
 ---
 
 P.S.:, for completeness sake, here the variations observered but without the expectation that that would add much more information.
 
 >   panic: ufs_dirbad: /usr: bad dir ino 46895494 at offset 114368: mangled
 > entry
 >   cpuid=1
 >   KDB: enter: panic
 >   [thread pid 42063 tid 100153]
 
 This is, as one may expect, the only line that changes:
 
    [thread pid 66833 tid 100168]
 
 or, upon ls of the directory which used to have the inode no. 46895494:
 
    [thread pid 3244 tid 100154]
 
 >   Stopped at      kdb_enter+0x3a movl    $0,kdb_why
 -- 
 GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
 Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: linimon 
State-Changed-When: Thu Jun 10 00:42:13 UTC 2010 
State-Changed-Why:  
Misfiled followup to kern/147420; content migrated. 


Responsible-Changed-From-To: gnats-admin->freebsd-bugs 
Responsible-Changed-By: linimon 
Responsible-Changed-When: Thu Jun 10 00:42:13 UTC 2010 
Responsible-Changed-Why:  

http://www.freebsd.org/cgi/query-pr.cgi?pr=147496 
>Unformatted:
