[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120801074845.GA13030@gmail.com>
Date: Wed, 1 Aug 2012 15:48:46 +0800
From: Zheng Liu <gnehzuil.liu@...il.com>
To: Tomasz Chmielewski <mangoo@...g.org>
Cc: semenko@...detics.net, linux-ext4@...r.kernel.org,
semenko@...m.mit.edu, tytso@....edu, djwong@...ibm.com
Subject: Re: "Unknown code" error when enabling metadata_csum on ext4 raid1
device
On Wed, Aug 01, 2012 at 02:16:41PM +0700, Tomasz Chmielewski wrote:
> 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?
Are these messages printed before you enable metadata_csum feature?
Regards,
Zheng
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists