From: Andreas Dilger <adilger@dilger.ca>
To: Pavel Machek <pavel@ucw.cz>
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 13:17:37 -0600 [thread overview]
Message-ID: <9BEA347C-2246-4746-95A4-0E00E0369816@dilger.ca> (raw)
In-Reply-To: <20140704172104.GA4877@xo-6d-61-c0.localdomain>
[-- Attachment #1: Type: text/plain, Size: 901 bytes --]
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: ...
Cheers, Andreas
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2014-07-04 19:17 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-26 20:20 ext4: total breakdown on USB hdd, 3.0 kernel Pavel Machek
2014-06-26 20:30 ` Pavel Machek
2014-06-26 20:50 ` Pavel Machek
2014-06-27 2:48 ` Theodore Ts'o
2014-06-27 2:46 ` Theodore Ts'o
2014-06-29 20:25 ` Pavel Machek
2014-06-29 21:04 ` Theodore Ts'o
2014-06-30 6:46 ` Pavel Machek
2014-06-30 13:43 ` Theodore Ts'o
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 [this message]
2014-07-04 20:33 ` Pavel Machek
2014-07-04 22:18 ` Andreas Dilger
2014-07-05 22:17 ` Theodore Ts'o
2014-06-27 8:23 ` ext4: total breakdown on USB hdd, 3.0 kernel Oliver Neukum
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=9BEA347C-2246-4746-95A4-0E00E0369816@dilger.ca \
--to=adilger@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=pavel@ucw.cz \
--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.