From: Ted Ts'o <tytso@mit.edu>
To: Stuart Pook <slp4725@pook.it>
Cc: linux-ext4@vger.kernel.org
Subject: Re: error ext4_mb_generate_buddy:726 & add_dirent_to_buf:1272 after online resize
Date: Sat, 29 Jan 2011 17:33:10 -0500 [thread overview]
Message-ID: <20110129223310.GD19287@thunk.org> (raw)
In-Reply-To: <4D44919C.6010404@pook.it>
On Sat, Jan 29, 2011 at 11:15:56PM +0100, Stuart Pook wrote:
> I am getting these message about once a day. Each message arrives 24 hours amd a few minuted after the last message, wierd. Inode 262145 is a directory that I created just after the online resize of the filesystem.
Sorry for my lack of response. I've been in Brisbane for the past
week attending linux.conf.au. This message which you are seeing:
> /var/log/syslog:Jan 29 17:57:21 kooka kernel: : [1125159.904008] EXT4-fs (dm-28): error count: 11
> /var/log/syslog:Jan 29 17:57:21 kooka kernel: : [1125159.904014] EXT4-fs (dm-28): initial error at 1295177566: ext4_mb_generate_buddy:726
> /var/log/syslog:Jan 29 17:57:21 kooka kernel: : [1125159.904017] EXT4-fs (dm-28): last error at 1295177566: add_dirent_to_buf:1272: inode 262145: block 1048578
... 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
...and the most recent error was at:
% date -d @1295177566
Sun Jan 16 06:32:46 EST 2011
If you upgrade to e2fsck 1.41.14, it will reset the error counter and
the first/last most recent errors. 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. 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): ..."
Hope this helps,
- Ted
next prev parent reply other threads:[~2011-01-29 22:33 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 [this message]
2011-02-01 11:45 ` Stuart Pook
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=20110129223310.GD19287@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=slp4725@pook.it \
/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.