linux-ext4 - Re: ext4: media error but where?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <9BEA347C-2246-4746-95A4-0E00E0369816@dilger.ca>
Date:	Fri, 4 Jul 2014 13:17:37 -0600
From:	Andreas Dilger <adilger@...ger.ca>
To:	Pavel Machek <pavel@....cz>
Cc:	Theodore Ts'o <tytso@....edu>,
	Ext4 Developers List <linux-ext4@...r.kernel.org>
Subject: Re: ext4: media error but where?

On Jul 4, 2014, at 11:21 AM, Pavel Machek <pavel@....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






Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)