From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Sandeen Subject: Re: ext4_ext_check_inode: bad header/extent in inode Date: Fri, 24 Apr 2009 16:23:13 -0500 Message-ID: <49F22DC1.4080700@redhat.com> References: <49F0642A.4000704@redhat.com> <20090423204059.GM2723@mit.edu> <20090424032028.GB7949@mit.edu> <20090424120004.GD7949@mit.edu> <49F1B24B.7080308@redhat.com> <49F22244.5040407@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Theodore Tso , linux-ext4@vger.kernel.org To: Christian Kujau Return-path: Received: from mx2.redhat.com ([66.187.237.31]:53121 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754644AbZDXVXT (ORCPT ); Fri, 24 Apr 2009 17:23:19 -0400 In-Reply-To: Sender: linux-ext4-owner@vger.kernel.org List-ID: Christian Kujau wrote: > On Fri, 24 Apr 2009, Eric Sandeen wrote: >> They don't actually have any blocks, > > So, they could be just deleted anyway? While I cannot do so with "rm", > debugfs was able to (thanks for the hint!): > > http://nerdbynature.de/bits/2.6.30-rc3/screenlog2.txt > > Now I have only 2 files left triggering the "Input/output error" - I could > kill these off with debugfs as well, then the filesystem should be clean > again. Still, I wish fsck had done this for me :-) It will.... soon... :) -Eric