From: Pavel Machek <pavel@ucw.cz>
To: Andreas Dilger <adilger@dilger.ca>
Cc: Theodore Ts'o <tytso@mit.edu>,
Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Re: ext4: media error but where?
Date: Fri, 4 Jul 2014 22:33:09 +0200 [thread overview]
Message-ID: <20140704203309.GA28107@amd.pavel.ucw.cz> (raw)
In-Reply-To: <9BEA347C-2246-4746-95A4-0E00E0369816@dilger.ca>
On Fri 2014-07-04 13:17:37, Andreas Dilger wrote:
> On Jul 4, 2014, at 11:21 AM, Pavel Machek <pavel@ucw.cz> wrote:
> >>> pavel@duo:~$ uname -a
> >>> Linux duo 3.15.0-rc8+ #365 SMP Mon Jun 9 09:18:29 CEST 2014 i686
> >>> GNU/Linux
> >>>
> >>> EXT4-fs (sda3): error count: 11
> >>> EXT4-fs (sda3): initial error at 1401714179: ext4_mb_generate_buddy:756
> >>> EXT4-fs (sda3): last error at 1401714179: ext4_reserve_inode_write:4877
> >>>
> >>> That sounds like media error to me?
> >>
> >> If you search your system logs since the last fsck, you should find 11
> >> instances of "EXT4-fs error" message, which means that there was some
> >> file system inconsisntencies detected. The first error was detected at:
> >>
> >> % date -d @1401714179
> >> Mon Jun 2 09:02:59 EDT 2014
> >
> > Interesting. I always assumed 140... was block number.
>
> Maybe it is worthwhile to improve this error message to be:
>
> EXT4-fs (sda3): initial error at time 1401714179: ...
I'm glad you suggested it. I actually done a patch before reading
this. What about:
---
Make it clear that values printed are times, and that it is error
since last fsck. Also add note about fsck version required.
Signed-off-by: Pavel Machek <pavel@ucw.cz>
diff --git a/fs/ext4/super.c b/fs/ext4/super.c
index b9b9aab..3423947 100644
--- a/fs/ext4/super.c
+++ b/fs/ext4/super.c
@@ -2809,10 +2809,11 @@ static void print_daily_error_info(unsigned long arg)
es = sbi->s_es;
if (es->s_error_count)
- ext4_msg(sb, KERN_NOTICE, "error count: %u",
+ /* fsck newer than v1.41.13 is needed to clean this condition. */
+ ext4_msg(sb, KERN_NOTICE, "error count since last fsck: %u",
le32_to_cpu(es->s_error_count));
if (es->s_first_error_time) {
- printk(KERN_NOTICE "EXT4-fs (%s): initial error at %u: %.*s:%d",
+ printk(KERN_NOTICE "EXT4-fs (%s): initial error at time %u: %.*s:%d",
sb->s_id, le32_to_cpu(es->s_first_error_time),
(int) sizeof(es->s_first_error_func),
es->s_first_error_func,
@@ -2826,7 +2827,7 @@ static void print_daily_error_info(unsigned long arg)
printk("\n");
}
if (es->s_last_error_time) {
- printk(KERN_NOTICE "EXT4-fs (%s): last error at %u: %.*s:%d",
+ printk(KERN_NOTICE "EXT4-fs (%s): last error at time %u: %.*s:%d",
sb->s_id, le32_to_cpu(es->s_last_error_time),
(int) sizeof(es->s_last_error_func),
es->s_last_error_func,
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2014-07-04 20:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140626202021.GA8512@xo-6d-61-c0.localdomain>
[not found] ` <20140626203052.GA9449@xo-6d-61-c0.localdomain>
[not found] ` <20140627024659.GF6826@thunk.org>
[not found] ` <20140629202516.GA11430@amd.pavel.ucw.cz>
[not found] ` <20140629210428.GD2162@thunk.org>
[not found] ` <20140630064644.GA23079@amd.pavel.ucw.cz>
[not found] ` <20140630134313.GA3753@thunk.org>
2014-07-04 10:23 ` ext4: media error but where? Pavel Machek
2014-07-04 12:11 ` Theodore Ts'o
2014-07-04 17:21 ` Pavel Machek
2014-07-04 18:06 ` Pavel Machek
2014-07-04 18:56 ` Theodore Ts'o
2014-07-06 13:32 ` Pavel Machek
2014-07-06 13:43 ` Pavel Machek
2014-07-06 18:29 ` Theodore Ts'o
2014-07-06 21:37 ` Pavel Machek
2014-07-07 1:00 ` Theodore Ts'o
2014-07-07 18:55 ` Pavel Machek
2014-07-07 23:18 ` 3.16-rc, ext4: oopses, OOMs after hard powerdown Pavel Machek
2014-07-07 23:21 ` ext4: media error but where? Theodore Ts'o
2014-07-04 19:17 ` Andreas Dilger
2014-07-04 20:33 ` Pavel Machek [this message]
2014-07-04 22:18 ` Andreas Dilger
2014-07-05 22:17 ` Theodore Ts'o
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=20140704203309.GA28107@amd.pavel.ucw.cz \
--to=pavel@ucw.cz \
--cc=adilger@dilger.ca \
--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 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).