From: Andreas Dilger <adilger@clusterfs.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
Jan De Luyck <ml_linuxkernel_20060528@kcore.org>
Subject: Re: Fw: EXT3-fs warning (device sdd2): dx_probe: Unrecognised inode hash code 232
Date: Fri, 9 Mar 2007 14:00:37 -0700 [thread overview]
Message-ID: <20070309210037.GY5823@schatzie.adilger.int> (raw)
In-Reply-To: <20070309074014.10ba0e88.akpm@linux-foundation.org>
On Mar 09, 2007 07:40 -0800, Andrew Morton wrote:
> EXT3-fs warning (device sdd2): dx_probe: Unrecognised inode hash code 232
> Assertion failure in dx_probe() at fs/ext3/namei.c:384: "dx_get_limit(entries)
> == dx_root_limit(dir, root->info.info_length)"
Looks like corrupted on-disk or in-memory htree metadata. We should
probably handle this more gracefully, if indeed it is corrupted on disk.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
prev parent reply other threads:[~2007-03-09 21:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-09 15:40 Fw: EXT3-fs warning (device sdd2): dx_probe: Unrecognised inode hash code 232 Andrew Morton
2007-03-09 21:00 ` Andreas Dilger [this message]
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=20070309210037.GY5823@schatzie.adilger.int \
--to=adilger@clusterfs.com \
--cc=akpm@linux-foundation.org \
--cc=linux-ext4@vger.kernel.org \
--cc=ml_linuxkernel_20060528@kcore.org \
/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