Re: kern/147496: ufs_dirbad, nullfs, jail (was: kern/147420: [nfs] kldload nfs modules causes nfs-aware kernel panic after a while)

2010-06-09 Thread linimon
Synopsis: ufs_dirbad, nullfs, jail (was: kern/147420: [nfs] kldload nfs modules causes nfs-aware kernel panic after a while) 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/147

ufs_dirbad, nullfs, jail (was: kern/147420: [nfs] kldload nfs modules causes nfs-aware kernel panic after a while)

2010-06-05 Thread Peter Cornelius
Hi, After two more failures, I now found the offending inode with find /usr -inum 46895494 and removed that directory with rm -rf . 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 w

Re: kern/147420: [nfs] kldload nfs modules causes nfs-aware kernel panic after a while

2010-06-04 Thread Peter Cornelius
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 bet

kern/147420: [nfs] kldload nfs modules causes nfs-aware kernel panic after a while

2010-06-03 Thread Peter Cornelius
>Number: 147420 >Category: kern >Synopsis: [nfs] kldload nfs modules causes nfs-aware kernel panic after >a while >Confidential: no >Severity: non-critical >Priority: low >Responsible:freebsd-bugs >State: open >Quarter: >Keywords: >Dat