All of lore.kernel.org
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: "Dâniel Fraga" <fragabr@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Kernel 3.7.0: bad header/extent
Date: Sat, 15 Dec 2012 21:27:53 -0500	[thread overview]
Message-ID: <20121216022753.GD9016@thunk.org> (raw)
In-Reply-To: <kainf9$btc$1@ger.gmane.org>

On Sat, Dec 15, 2012 at 06:44:26PM -0200, Dâniel Fraga wrote:
> 	After upgrading from kernel 3.6.0 to 3.7.0 (x86-64) I got this:
> 
> Dec 15 18:38:28 tux kernel: EXT4-fs error (device sda2): 
> ext4_ext_check_inode:462: inode #9311628: comm less: bad header/extent:
> invalid extent entries - magic f30a, entries 1, max 4(4), depth 0(0)
> 
> 	So I tried to run e2fsck and it "fixed" inode 9311628. Running 
> e2fsck again doesn't detect any errors, but the problem remains.

What do you mean "the problem remains"?  Are you getting the same
EXT4-fs error message when you try to access the file?

Can you send the output of the command:

	debugfs -R "stat <9311628>"/dev/sda2

Thanks!!

						- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2012-12-16  2:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-15 20:44 Kernel 3.7.0: bad header/extent Dâniel Fraga
2012-12-16  2:27 ` Theodore Ts'o [this message]
2012-12-16  3:00   ` Dâniel Fraga
2012-12-16  3:51     ` Theodore Ts'o
2012-12-16  5:39       ` Dâniel Fraga
2012-12-16  6:08         ` Andreas Dilger
2012-12-16 14:50           ` Theodore Ts'o
2012-12-16 23:52             ` Dâniel Fraga

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=20121216022753.GD9016@thunk.org \
    --to=tytso@mit.edu \
    --cc=fragabr@gmail.com \
    --cc=linux-ext4@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.