On 08/01/2012 02:19 PM, Zheng Liu wrote: > Hi Nick and Tomasz, > > Could you please try this patch? It seems that the problem is because > error code doesn't be clear. Hi, didn't try the patch yet, but I've noticed the following in dmesg since 3.5: [69004.637293] EXT4-fs warning (device sda1): dx_probe:732: Corrupt dir inode 524293, running e2fsck is recommended. [69004.637330] EXT4-fs warning (device sda1): dx_probe:647: dx entry: limit != root limit [69004.637335] EXT4-fs warning (device sda1): dx_probe:732: Corrupt dir inode 524293, running e2fsck is recommended. [69004.637365] EXT4-fs warning (device sda1): dx_probe:647: dx entry: limit != root limit [69004.637370] EXT4-fs warning (device sda1): dx_probe:732: Corrupt dir inode 524293, running e2fsck is recommended. Could this be related? -- Tomasz Chmielewski http://blog.wpkg.org -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
