On Wed, Aug 01, 2012 at 02:51:43PM +0700, Tomasz Chmielewski wrote:

On 08/01/2012 02:48 PM, Zheng Liu wrote:

quoted

quoted

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?

Are these messages printed before you enable metadata_csum feature?

I didn't notice them before trying to enable metadata_csum feature.

On the other hand, enabling metadata_csum feature was pretty much
the first thing I've made after booting to 3.5 kernel on this
system, so it could be it changed something.

Yes, it will change something when you try to enable metadata_csum
feature in tune2fs.  So you'd better to run e2fsck to check your
filesystem IMHO.

Also, when I do:

	dumpe2fs -h /dev/sda1|grep metadata_csum

I don't see metadata_csum feature anywhere.

You won't see this feature until you can enable this feature successful.

Regards,
Zheng