From: Yongqiang Yang <xiaoqiangnk@gmail.com>
To: bugzilla-daemon@bugzilla.kernel.org
Cc: linux-ext4@vger.kernel.org
Subject: Re: [Bug 32182] New: EXT4-fs error: bad header/extent
Date: Fri, 1 Apr 2011 22:07:32 +0800 [thread overview]
Message-ID: <AANLkTimrBs1kdNmS7d2DoTwa=wRHRu5DZKhRdk7DpcA9@mail.gmail.com> (raw)
In-Reply-To: <bug-32182-13602@https.bugzilla.kernel.org/>
Could the bug be reproduced?
If so, how to?
On Wed, Mar 30, 2011 at 12:47 AM, <bugzilla-daemon@bugzilla.kernel.org> wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=32182
>
> Summary: EXT4-fs error: bad header/extent
> Product: File System
> Version: 2.5
> Kernel Version: 2.6.38.1
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: high
> Priority: P1
> Component: ext4
> AssignedTo: fs_ext4@kernel-bugs.osdl.org
> ReportedBy: ramses.rommel@gmail.com
> Regression: No
>
>
> I started noticing ext4-fs errors in my dmesg output, they look like this:
>
> EXT4-fs error (device sda2): ext4_ext_check_inode:428: inode #3760218: comm
> dropbox: bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth
> 0(0)
> EXT4-fs error (device sda2): ext4_ext_check_inode:428: inode #3760208: comm
> dropbox: bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth
> 0(0)
> EXT4-fs error (device sda2): ext4_ext_check_inode:428: inode #3760218: comm
> thunderbird-bin: bad header/extent: invalid magic - magic 0, entries 0, max
> 0(0), depth 0(0)
> EXT4-fs error (device sda2): ext4_ext_check_inode:428: inode #3760208: comm
> thunderbird-bin: bad header/extent: invalid magic - magic 0, entries 0, max
> 0(0), depth 0(0)
>
> I fsck'ed the partition which showed nothing but the regular output but said
> the file system was modified, after a reboot the same errors returned though.
> I'm using e2fsprogs 1.41.14 and linux 2.6.38.1 and after a downgrade to linux
> 2.6.37.5 the errors kept reappearing (I'll test 2.6.38.2 soon but I didn't find
> commit messages that seemed relevant).
>
> I ran debugfs on one of the inodes:
>
> % debugfs -R 'stat <3760208>' /dev/disk/by-label/home
> debugfs 1.41.14 (22-Dec-2010)
> Inode: 3760208 Type: regular Mode: 0644 Flags: 0x80000
> Generation: 231468018 Version: 0x00000001
> User: 1000 Group: 100 Size: 42
> File ACL: 0 Directory ACL: 0
> Links: 1 Blockcount: 0
> Fragment: Address: 0 Number: 0 Size: 0
> ctime: 0x4b2a09ff -- Thu Dec 17 11:37:51 2009
> atime: 0x4d909367 -- Mon Mar 28 15:55:51 2011
> mtime: 0x490976f8 -- Thu Oct 30 09:57:28 2008
> EXTENTS:
>
> I'm not sure what extra info to give you, but I'd be glad to provide stuff you
> need to reproduce/fix this.
>
> --
> Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You are watching the assignee of the bug.
> --
> 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
>
--
Best Wishes
Yongqiang Yang
--
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
next prev parent reply other threads:[~2011-04-01 14:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-29 16:47 [Bug 32182] New: EXT4-fs error: bad header/extent bugzilla-daemon
2011-04-01 14:07 ` Yongqiang Yang [this message]
2011-04-01 14:07 ` [Bug 32182] " bugzilla-daemon
2011-04-01 15:27 ` bugzilla-daemon
2011-04-01 15:29 ` bugzilla-daemon
2011-04-01 22:01 ` bugzilla-daemon
2011-04-01 23:21 ` bugzilla-daemon
2011-04-22 10:59 ` bugzilla-daemon
2011-06-06 19:59 ` bugzilla-daemon
2011-07-07 5:15 ` bugzilla-daemon
2011-07-07 14:45 ` bugzilla-daemon
2011-08-24 21:50 ` bugzilla-daemon
2012-08-20 15:23 ` bugzilla-daemon
2012-08-20 20:06 ` bugzilla-daemon
2012-08-21 0:44 ` bugzilla-daemon
2012-08-21 20:33 ` bugzilla-daemon
2012-08-21 21:34 ` bugzilla-daemon
2015-03-05 14:32 ` bugzilla-daemon
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='AANLkTimrBs1kdNmS7d2DoTwa=wRHRu5DZKhRdk7DpcA9@mail.gmail.com' \
--to=xiaoqiangnk@gmail.com \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--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 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).