From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 32182] EXT4-fs error: bad header/extent
Date: Tue, 21 Aug 2012 20:33:31 +0000 (UTC) [thread overview]
Message-ID: <20120821203331.4E54611FC6C@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-32182-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=32182
--- Comment #14 from Peter Hanecak <hany+kernel.org@hany.sk> 2012-08-21 20:33:30 ---
Reboot + fsck was done quite a lot of times since it started occuring. Some
bugs do get found and fixed but the message never goes away. I have no further
info to open new bug.
Any suggestions as to what I might try to either fix the inode or compile some
more information so as to file bug report? Thanks in advance.
--
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:[~2012-08-21 20:33 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
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 [this message]
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=20120821203331.4E54611FC6C@bugzilla.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).