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: 3.16-rc, ext4: oopses, OOMs after hard powerdown
Date: Tue, 8 Jul 2014 01:18:33 +0200 [thread overview]
Message-ID: <20140707231833.GA31501@amd.pavel.ucw.cz> (raw)
In-Reply-To: <20140707185543.GA26056@amd.pavel.ucw.cz>
[-- Attachment #1: Type: text/plain, Size: 1482 bytes --]
Hi!
With 3.16-rc3, I did deliberate powerdown by holding down power key
(not a clean shutdown). On the next boot, I got some scary messages
about data corruption, "filesystem has errors, check forced", "reboot
linux". Unfortunately, that made the scary messages gone forever (I
tried ^S, was not fast enough), as system rebooted.
But it seems I have more of the bad stuff coming:
Mounting local filesystems threw an oops and then mount was killed due
to out-of-memory. I lost sda2 (or /data) filesystem. Then both sda3
(root) and sda2 gave me. But there's no disk error either in smart or
in syslog.
Jul 8 01:03:18 duo kernel: EXT4-fs (sda3): error count: 2
Jul 8 01:03:18 duo kernel: EXT4-fs (sda3): initial error at
1404773782: ext4_mb_generate_buddy:757
Jul 8 01:03:18 duo kernel: EXT4-fs (sda3): last error at 1404773782:
ext4_mb_generate_buddy:757
Jul 8 01:05:44 duo kernel: EXT4-fs (sda2): error count: 12
Jul 8 01:05:44 duo kernel: EXT4-fs (sda2): initial error at
1404773906: ext4_mb_generate_buddy:757
Jul 8 01:05:44 duo kernel: EXT4-fs (sda2): last error at 1404774058:
ext4_journal_check_start:56
(Thinkpad x60 with Hitachi HTS... SATA disk).
I attach complete syslog from the boot up... it should have everything
relevant.
I'm running fsck -f on sda3 now. I'd like to repair sda2 tommorow.
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: delme.gz --]
[-- Type: application/octet-stream, Size: 23593 bytes --]
next prev parent reply other threads:[~2014-07-07 23:18 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 ` Pavel Machek [this message]
2014-07-07 23:21 ` 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=20140707231833.GA31501@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).