From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 51431] ext4_mb_generate_buddy self ext4 errors
Date: Sat, 8 Dec 2012 16:35:08 +0000 (UTC) [thread overview]
Message-ID: <20121208163508.4DB5911FC70@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-51431-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=51431
Eric Sandeen <sandeen@redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sandeen@redhat.com
--- Comment #1 from Eric Sandeen <sandeen@redhat.com> 2012-12-08 16:35:07 ---
The messages you see are telling you about a message which happened int the
past.
ext4 stores errors, and reports them again every 24h, which seems to be a
source of confusion for most people who encounter it. :(
this:
> initial error at 1354656587
means that it happened at that unix timestamp, i.e.
# date -u --date="1970-01-01 1354656587 sec GMT"
Tue Dec 4 21:29:47 UTC 2012
Newer e2fsck should clear the message, as of about version 1.41.14 IIRC. Older
e2fsck does not, and the kernel message will repeat every 24h ad infinitum
until it gets cleared.
-Eric
--
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-12-08 16:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-08 11:41 [Bug 51431] New: ext4_mb_generate_buddy self ext4 errors bugzilla-daemon
2012-12-08 11:48 ` [Bug 51431] " bugzilla-daemon
2012-12-08 16:35 ` bugzilla-daemon [this message]
2012-12-08 16:36 ` bugzilla-daemon
2012-12-08 16:38 ` bugzilla-daemon
2012-12-08 16:42 ` bugzilla-daemon
2012-12-08 16:44 ` bugzilla-daemon
2012-12-08 16:55 ` bugzilla-daemon
2012-12-08 16:59 ` bugzilla-daemon
2013-11-19 18:21 ` bugzilla-daemon
2013-11-19 18:21 ` 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=20121208163508.4DB5911FC70@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).