From: Zheng Liu <gnehzuil.liu@gmail.com>
To: Tomasz Chmielewski <mangoo@wpkg.org>
Cc: semenko@syndetics.net, linux-ext4@vger.kernel.org,
semenko@alum.mit.edu, tytso@mit.edu, djwong@us.ibm.com
Subject: Re: "Unknown code" error when enabling metadata_csum on ext4 raid1 device
Date: Wed, 1 Aug 2012 15:48:46 +0800 [thread overview]
Message-ID: <20120801074845.GA13030@gmail.com> (raw)
In-Reply-To: <5018D7D9.6080709@wpkg.org>
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
next prev parent reply other threads:[~2012-08-01 7:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 2:53 "Unknown code" error when enabling metadata_csum on ext4 raid1 device Nick Semenkovich
2012-08-01 7:19 ` Zheng Liu
2012-08-01 7:16 ` Tomasz Chmielewski
2012-08-01 7:48 ` Zheng Liu [this message]
2012-08-01 7:51 ` Tomasz Chmielewski
2012-08-01 8:17 ` Zheng Liu
2012-08-02 3:43 ` Nick Semenkovich
2012-08-02 9:58 ` Zheng Liu
2012-08-03 4:01 ` Theodore Ts'o
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120801074845.GA13030@gmail.com \
--to=gnehzuil.liu@gmail.com \
--cc=djwong@us.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=mangoo@wpkg.org \
--cc=semenko@alum.mit.edu \
--cc=semenko@syndetics.net \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).