misc/185448: ext2fs corrupt dir inode, FreeBSD 10 RC3

[Bob Sullivan]

>Number:         185448
>Category:       misc
>Synopsis:       ext2fs corrupt dir inode, FreeBSD 10 RC3
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Jan 03 16:40:00 UTC 2014
>Closed-Date:
>Last-Modified:
>Originator:     Bob Sullivan
>Release:        FreeBSD 10 RC3 i386
>Organization:
N/A
>Environment:
FreeBSD panther.local 10.0-RC3 FreeBSD 10.0-RC3 #0 r259778: Tue Dec 24 04:35:46 UTC 2013     root at snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC  i386
>Description:
After I upgraded from FreeBSD 8 to 10 RC3 (dual boot Linux/FreeBSD), on Linux, I noticed this error in dmesg (which never appeared on FreeBSD 8):

syslog.1:Dec 29 14:49:56 pc kernel: [ 4969.426736] EXT3-fs (sda5): warning: dx_probe: Unrecognised inode hash code 44
syslog.1:Dec 29 14:49:56 pc kernel: [ 4969.426748] EXT3-fs (sda5): warning: dx_probe: Corrupt dir inode 4194305, running e2fsck is recommended.

However, I compared the directory against a backup and no data was lost, and Linux fsck didn't find any real problems (this bug seems benign).

bobsullivan1960 /-at-/ gmail /-/ com

>How-To-Repeat:
Isn't reproducible, unfortuantely.


>Fix:
N/A

>Release-Note:
>Audit-Trail:
>Unformatted: