From: bugzilla-daemon@bugzilla.kernel.org
Subject: [Bug 14354] Bad corruption with 2.6.32-rc1 and upwards
Date: Mon, 26 Oct 2009 19:13:15 GMT
Message-ID: <200910261913.n9QJDFXq027084@demeter.kernel.org>
References:
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
To: linux-ext4@vger.kernel.org
Return-path:
Received: from demeter.kernel.org ([140.211.167.39]:34001 "EHLO
demeter.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
with ESMTP id S1753624AbZJZTNM (ORCPT
); Mon, 26 Oct 2009 15:13:12 -0400
Received: from demeter.kernel.org (localhost.localdomain [127.0.0.1])
by demeter.kernel.org (8.14.2/8.14.2) with ESMTP id n9QJDFmq027085
for ; Mon, 26 Oct 2009 19:13:15 GMT
In-Reply-To:
Sender: linux-ext4-owner@vger.kernel.org
List-ID:
http://bugzilla.kernel.org/show_bug.cgi?id=14354
Linus Torvalds changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |torvalds@linux-foundation.o
| |rg
--- Comment #119 from Linus Torvalds 2009-10-26 19:13:13 ---
It seems to be only after an unclean shutdown for me, judging by some judicious
grepping of /var/log/messgaes. At least the ext4 error messages in dmesg only
seem to happen when I don't see the line "Kernel logging (proc) stopped." in
the messages file before the new boot.
Of course, maybe the problem is caused by - or even just made visible by - not
the unclean shutdown itself, but the fsck or the journal replay which is just
triggered by the unclean shutdown. IOW, it could be secondary damage. That
sounds unlikely, though.
I dunno. As mentioned, I don't think that I was doing anything particularly
write-heavy when I forced the unclean shutdown.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.