From: Stuart Pook <stuart8761@pook.it>
To: Ted Ts'o <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org
Subject: Re: error ext4_mb_generate_buddy:726 & add_dirent_to_buf:1272 after online resize
Date: Tue, 01 Feb 2011 12:45:32 +0100 [thread overview]
Message-ID: <4D47F25C.9060608@pook.it> (raw)
In-Reply-To: <20110129223310.GD19287@thunk.org>
On 29/01/11 23:33, Ted Ts'o wrote:
> ... is strictly speaking not an error. It is a status report
> indicating that in the past your file system had suffered an error.
> The first error was at 1295177566 seconds past the epoch, or at:
>
> % date -d @1295177566
> Sun Jan 16 06:32:46 EST 2011
:; date -d @1295177566
Sun Jan 16 12:32:46 CET 2011
It's little later in my timezone and that was just after I resized my file system.
> If you upgrade to e2fsck 1.41.14, it will reset the error counter and
> the first/last most recent errors.
I upgraded to 1.41.14, ran e2fsck and the messages have stopped.
We still don't know what caused the initial errors (which have now vanished). As they started just after an online resize I'd guess that there were (are?) some bugs in that code. I'll avoid doing online resizes of my ext4 file systems for the moment.
> The idea behind this is that
> sometimes people aren't paying close attention to their
> /var/log/messages file, so this is a periodic informational reminder,
> printed once a day.
That's a good idea. Once you know how to translate 1295177566 into a real time, you can go and look in the logs for the correct day.
> If you are creating shell scripts to find errors,
> match on "EXT4-fs Error", for example "EXT4-fs error (dm-28): disk on
> fire". Warnings will be denoted with "EXT4-fs warning", and and
> information messages, such as this one just start with "EXT4-fs", as
> in "EXT4-fs (dm-28): ..."
perhaps it would be better if they started with "EXT4-fs repeat message" (or something that you might be able to find with google)
> Hope this helps,
It sure does, thanks
Stuart
prev parent reply other threads:[~2011-02-01 11:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <S1752440Ab1APNtL/20110116134911Z+826@vger.kernel.org>
2011-01-16 14:03 ` error ext4_mb_generate_buddy:726 & add_dirent_to_buf:1272 after online resize Stuart Pook
2011-01-16 14:28 ` Stuart Pook
2011-01-29 22:15 ` Stuart Pook
2011-01-29 22:33 ` Ted Ts'o
2011-02-01 11:45 ` Stuart Pook [this message]
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=4D47F25C.9060608@pook.it \
--to=stuart8761@pook.it \
--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.