Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 23 Dec 2014 11:57:38 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-fs@FreeBSD.org
Subject:   [Bug 193389] [panic] ufs_dirbad: /: bad dir
Message-ID:  <bug-193389-3630-aN4Dqp8DZY@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-193389-3630@https.bugs.freebsd.org/bugzilla/>
References:  <bug-193389-3630@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193389

--- Comment #5 from mikej@mikej.com ---
(In reply to mikej from comment #3)
> I am also getting this error under current.
> 
> FreeBSD d620 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r275582: Mon Dec  8
> 02:36:47 UTC 2014     root@grind.freebsd.org:/usr/obj/usr/src/sys/GENERIC 
> i386
> 
> panic: ufs_dirbad: /: bad dir ino 8668611 at offset 12288: mangled entry
> 
> http://mail.mikej.com/core.txt.0
> http://mail.mikej.com/info.0
> 
> http://mail.mikej.com/core.txt.1
> http://mail.mikej.com/info.1
> 
> http://mail.mikej.com/smartctl-a.ada0
> http://mail.mikej.com/dmesg.d620
> 
> I am getting DMA errors on the device though, not sure if this is a driver
> or disk problem.  This is a SSD device, the laptop had been running with a
> Seagate Momentus under windows and linux without issue.
> 
> I will swap drives tonight and see if the problem is isolated to the SSD or
> not and report back and perform any other suggested tasks for trouble
> shooting.
> 
> Now this is so odd I will mention it but I can't fathom why it would matter,
> but all my panics have always happened immediately after running "man".  So
> far no panics while running X, firefox, and a lot of other applications.
> 
> Thanks.

I have spent some time with this and isolated my problem to the SSD drive that
I was using.  I have not determined why the SSD drive had caused an issue, but
after installing an WD3200BEVT-00AORTO and letting the laptop churn for days I
have not been able to reproduce my original problem.

Lastly, find / -xdev -inum 8668611 -print did always produce the fault, the
issue was in man page directories (I don't remember the exact path).

Consider this resolved for me.

--mikej

-- 
You are receiving this mail because:
You are on the CC list for the bug.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-193389-3630-aN4Dqp8DZY>