From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@bugzilla.kernel.org
Subject: [Bug 32182] EXT4-fs error: bad header/extent
Date: Fri, 1 Apr 2011 15:29:39 GMT
Message-ID: <201104011529.p31FTdtk025737@demeter2.kernel.org>
References:
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
To: linux-ext4@vger.kernel.org
Return-path:
Received: from demeter2.kernel.org ([140.211.167.42]:57148 "EHLO
demeter2.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
with ESMTP id S1757897Ab1DAP3j (ORCPT
); Fri, 1 Apr 2011 11:29:39 -0400
Received: from demeter2.kernel.org (localhost.localdomain [127.0.0.1])
by demeter2.kernel.org (8.14.4/8.14.3) with ESMTP id p31FTdNj025741
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
for ; Fri, 1 Apr 2011 15:29:39 GMT
In-Reply-To:
Sender: linux-ext4-owner@vger.kernel.org
List-ID:
https://bugzilla.kernel.org/show_bug.cgi?id=32182
Eric Sandeen changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sandeen@redhat.com
--- Comment #3 from Eric Sandeen 2011-04-01 15:29:37 ---
If most recent fsck doesn't find anything, but runtime finds errors, perhaps
you can provide a bzip2'd e2image -r of the fileystem in question? If
filenames are sensitive/private, there is an option to scramble them.
That way we can see what it's finding, why it's complaining, and why fsck
doesn't seem to care.
It's interesting that the "bad" data is all 0s though. What kind of storage is
this?
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.