Summary: | [ufs] [panic] ufs_dirbad, nullfs, jail panic (corrupt inode) | ||
---|---|---|---|
Product: | Base System | Reporter: | pcc <pcc> |
Component: | kern | Assignee: | freebsd-bugs (Nobody) <bugs> |
Status: | Closed Overcome By Events | ||
Severity: | Affects Only Me | CC: | chris, rew |
Priority: | Normal | ||
Version: | 8.1-PRERELEASE | ||
Hardware: | Any | ||
OS: | Any |
Description
pcc
2010-06-03 09:00:02 UTC
Responsible Changed From-To: freebsd-bugs->freebsd-fs Over to maintainer(s). 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 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 For bugs matching the following criteria: Status: In Progress Changed: (is less than) 2014-06-01 Reset to default assignee and clear in-progress tags. Mail being skipped |