From: Andreas Dilger <adilger@sun.com>
To: Theodore Tso <tytso@mit.edu>
Cc: Christian Kujau <lists@nerdbynature.de>,
Eric Sandeen <sandeen@redhat.com>,
linux-ext4@vger.kernel.org
Subject: Re: ext4_ext_check_inode: bad header/extent in inode
Date: Fri, 24 Apr 2009 01:09:43 -0600 [thread overview]
Message-ID: <20090424070943.GR3209@webber.adilger.int> (raw)
In-Reply-To: <20090424032028.GB7949@mit.edu>
On Apr 23, 2009 23:20 -0400, Theodore Ts'o wrote:
> On Thu, Apr 23, 2009 at 03:15:10PM -0700, Christian Kujau wrote:
> > On Thu, 23 Apr 2009, Theodore Tso wrote:
> > > Eventually I might need a raw e2image dump, i.e.:
> > >
> > > e2image -r /dev/md0 - | bzip2 > /var/tmp/md0.e2i.bz2
> >
> > I've put the raw e2image dump on http://nerdbynature.de/bits/2.6.30-rc2/
> > Do you still need the dump without the "-r"?
>
> Nope, the raw e2image file was perfect. This was actually a problem I
> knew about, and wanted to get fixed before the e2fsprogs 1.41.5
> release. The problem was that i_file_acl_high was set and the kernel
> unconditionally checks for it even though the INCOMPAT_64_BITS flag is
> not set.
Maybe I'm missing something, but how can i_file_acl_high being used
cause a problem with the file extent maps?
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
next prev parent reply other threads:[~2009-04-24 7:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-23 12:15 ext4_ext_check_inode: bad header/extent in inode Christian Kujau
2009-04-23 12:50 ` Eric Sandeen
2009-04-23 19:04 ` Christian Kujau
2009-04-23 20:40 ` Theodore Tso
2009-04-23 22:15 ` Christian Kujau
2009-04-24 3:20 ` Theodore Tso
2009-04-24 7:09 ` Andreas Dilger [this message]
2009-04-24 11:58 ` Theodore Tso
2009-04-24 20:09 ` Andreas Dilger
2009-04-24 8:57 ` Christian Kujau
2009-04-24 9:40 ` Christian Kujau
2009-04-24 12:00 ` Theodore Tso
2009-04-24 12:36 ` Eric Sandeen
2009-04-24 12:42 ` Eric Sandeen
2009-04-24 20:21 ` Christian Kujau
2009-04-24 20:34 ` Eric Sandeen
2009-04-24 20:59 ` Theodore Tso
2009-04-24 22:54 ` [PATCH] ext4: Do not try to validate extents on special files Theodore Ts'o
2009-04-24 21:02 ` ext4_ext_check_inode: bad header/extent in inode Christian Kujau
2009-04-24 21:23 ` Eric Sandeen
2009-04-24 20:41 ` Christian Kujau
2009-04-23 20:51 ` Andreas Dilger
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=20090424070943.GR3209@webber.adilger.int \
--to=adilger@sun.com \
--cc=linux-ext4@vger.kernel.org \
--cc=lists@nerdbynature.de \
--cc=sandeen@redhat.com \
--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).