From: Tomasz Chmielewski <mangoo@wpkg.org>
To: 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, 01 Aug 2012 14:51:43 +0700 [thread overview]
Message-ID: <5018E00F.1000207@wpkg.org> (raw)
In-Reply-To: <20120801074845.GA13030@gmail.com>
On 08/01/2012 02:48 PM, Zheng Liu wrote:
>> 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.
Also, when I do:
dumpe2fs -h /dev/sda1|grep metadata_csum
I don't see metadata_csum feature anywhere.
--
Tomasz Chmielewski
http://blog.wpkg.org
next prev parent reply other threads:[~2012-08-01 7:51 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
2012-08-01 7:51 ` Tomasz Chmielewski [this message]
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=5018E00F.1000207@wpkg.org \
--to=mangoo@wpkg.org \
--cc=djwong@us.ibm.com \
--cc=linux-ext4@vger.kernel.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).