From: Pavel Machek <pavel@ucw.cz>
To: Theodore Ts'o <tytso@mit.edu>,
kernel list <linux-kernel@vger.kernel.org>,
adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org
Subject: Re: ext4: media error but where?
Date: Fri, 4 Jul 2014 20:06:51 +0200 [thread overview]
Message-ID: <20140704180651.GA22322@amd.pavel.ucw.cz> (raw)
In-Reply-To: <20140704172104.GA4877@xo-6d-61-c0.localdomain>
Hi!
> > What I need from people reporting problems:
> >
> > * What is the HDD/SSD/eMMC device involved
>
> SATA hdd, will get you exact data.
Hitachi HTS545050A7E380, got it from ps/3 at april 25, 2014, never had
problems according to smart.
> > * What kernel version were you running
>
> For last month? Various, 3.10 to 3.16-rc, mostly 3.15+.
>
> > * What distribution are you running (more so I know what the init
> > scripts might or might not have been doing vis-a-vis running fsck
> > after a crash)
>
> Debian 6.
6.0.9
> Is it possible that my fsck is so old it does not clear this "filesystem
> had error in past" flag? Because I strongly suspect I'll boot into
> init=/bin/bash, run fsck, it will tell me "all clean", and the messages
> will repeat in the middle of fsck run.
And indeed:
..init=/bin/bash
# fsck /dev/sda3
e2fsck 1.41.12
rootfs: clean
# date +%s
1404496...
#
EXT4-fs (sda3): error count: 11
EXT4-fs (sda3): initial error at 1401741...
...
(hand copied)
Thanks,
Pavel
--
(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 18:06 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 [this message]
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
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=20140704180651.GA22322@amd.pavel.ucw.cz \
--to=pavel@ucw.cz \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@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).