From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 32182] EXT4-fs error: bad header/extent
Date: Fri, 1 Apr 2011 15:27:22 GMT [thread overview]
Message-ID: <201104011527.p31FRMsF030659@demeter1.kernel.org> (raw)
In-Reply-To: <bug-32182-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=32182
--- Comment #2 from Ramses de Norre <ramses.rommel@gmail.com> 2011-04-01 15:27:22 ---
I don't have to do anything to reproduce it, the errors show up in dmesg while
starting up programs mostly. I also don't think there was a specific trigger
that caused it, just normal fs usage.
I guess there is either some corruption in my file system that fsck does not
fix or that the kernel is reporting errors while it shouldn't.
I can provide you with more debug info, but I'm not that familiar with the
tools to do so, if you could explain what data you need to understand where the
bug sits, I'd be happy to provide it to you.
HTH,
Ramses
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2011-04-01 15:27 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
2011-04-01 14:07 ` [Bug 32182] " bugzilla-daemon
2011-04-01 15:27 ` bugzilla-daemon [this message]
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=201104011527.p31FRMsF030659@demeter1.kernel.org \
--to=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).