Thread (9 messages) 9 messages, 4 authors, 2012-08-03

Re: "Unknown code" error when enabling metadata_csum on ext4 raid1 device

From: Zheng Liu <hidden>
Date: 2012-08-01 07:40:02

On Wed, Aug 01, 2012 at 02:16:41PM +0700, Tomasz Chmielewski wrote:
On 08/01/2012 02:19 PM, Zheng Liu wrote:
quoted
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?
Are these messages printed before you enable metadata_csum feature?

Regards,
Zheng
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help