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: ext4: media error but where?
Date: Fri, 4 Jul 2014 12:23:07 +0200 [thread overview]
Message-ID: <20140704102307.GA19252@amd.pavel.ucw.cz> (raw)
In-Reply-To: <20140630134313.GA3753@thunk.org>
Hi!
(Note that this drive is in thinkpad x60, and never met olpc or nor
had any problems).
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?
But there's nothing in smart:
SMART Error Log Version: 1
No Errors Logged
SMART Self-test log structure revision number 1
I rebooted (into 3.14), and fsck claims filesystem is marked as
clean...? I did fsck -f, no problems.
Heh, now fsck -cf runs, and I got the same kernel messages. fsck says:
"updating bad block inode", but it does not say how many badblocks it
found (if any). At the end it says "filesystem was modified" and
"reboot linux", so I assume it found something? OTOH dumpe2fs -b
/dev/sda3 does not report anything.
What is going on there?
Best regards,
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 10:23 UTC|newest]
Thread overview: 23+ 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 ` Pavel Machek [this message]
2014-07-04 12:11 ` ext4: media error but where? 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-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=20140704102307.GA19252@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
all inboxes | Powered by JetHome®