Summary: | [panic] ufs_dirbad: /: bad dir | ||
---|---|---|---|
Product: | Base System | Reporter: | sasamotikomi |
Component: | kern | Assignee: | Kirk McKusick <mckusick> |
Status: | Closed Works As Intended | ||
Severity: | Affects Only Me | CC: | adrian, fs, mckusick, mikej, sasamotikomi, stable |
Priority: | --- | ||
Version: | 10.0-RELEASE | ||
Hardware: | i386 | ||
OS: | Any |
Description
sasamotikomi
2014-09-06 12:14:48 UTC
Have you run a full fsck on the filesystem? -a (In reply to Adrian Chadd from comment #1) > Have you run a full fsck on the filesystem? > > > > -a Yes as in single user mode without journal, also I got this panic again, when update my pkg. 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. It appears that the offending directory has moved since your first run. Could you please run the following commands to find the offending directory: find / -xdev -inum 8668611 -print ls -ld <output path of the above command> find / -xdev -inum 1777399 -print ls -ld <output path of the above command> Also, as noted by Adrian Chadd in comment #1 include the output of a full fsck of the filesystem would be useful (after you have run the above commands). (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 Thanks for your followup. I will close this bug. Submitter has determined that the panic was caused by hardware problems with disk on his system. |