From: "Dâniel Fraga" <fragabr@gmail.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Kernel 3.7.0: bad header/extent
Date: Sun, 16 Dec 2012 01:00:25 -0200 [thread overview]
Message-ID: <50cd394d.0153650a.3b8d.ffffb917@mx.google.com> (raw)
In-Reply-To: <20121216022753.GD9016@thunk.org>
On Sat, 15 Dec 2012 21:27:53 -0500
Theodore Ts'o <tytso@mit.edu> wrote:
> > 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
Hi Ted! Yes, I get the same EXT4-fs message when I try to
access teh file. Here's the requested output:
debugfs 1.41.12 (17-May-2010)
Inode: 9311628 Type: regular Mode: 0644 Flags: 0x80000
Generation: 834245655 Version: 0x00000000:00000001
User: 0 Group: 0 Size: 7117
File ACL: 0 Directory ACL: 0
Links: 1 Blockcount: 0
Fragment: Address: 0 Number: 0 Size: 0
ctime: 0x4f76ba2c:537fd694 -- Sat Mar 31 05:02:52 2012
atime: 0x50ccaf85:c6d93344 -- Sat Dec 15 15:12:37 2012
mtime: 0x4f76ba2c:537fd694 -- Sat Mar 31 05:02:52 2012
crtime: 0x4f76ba2c:537fd694 -- Sat Mar 31 05:02:52 2012
Size of extra inode fields: 28
EXTENTS:
***
If you need more testing, just ask. Thanks!
--
Linux 3.7.0: Terrified Chipmunk
http://www.youtube.com/DanielFragaBR
http://www.libertarios.org.br
next prev parent reply other threads:[~2012-12-16 3:00 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
2012-12-16 3:00 ` Dâniel Fraga [this message]
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=50cd394d.0153650a.3b8d.ffffb917@mx.google.com \
--to=fragabr@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--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 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.