From: Eric Sandeen <sandeen@redhat.com>
To: Christian Kujau <lists@nerdbynature.de>
Cc: Theodore Tso <tytso@mit.edu>, linux-ext4@vger.kernel.org
Subject: Re: ext4_ext_check_inode: bad header/extent in inode
Date: Fri, 24 Apr 2009 16:23:13 -0500 [thread overview]
Message-ID: <49F22DC1.4080700@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.01.0904241359380.6162@bogon.housecafe.de>
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
next prev parent reply other threads:[~2009-04-24 21:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-23 12:15 ext4_ext_check_inode: bad header/extent in inode Christian Kujau
2009-04-23 12:50 ` Eric Sandeen
2009-04-23 19:04 ` Christian Kujau
2009-04-23 20:40 ` Theodore Tso
2009-04-23 22:15 ` Christian Kujau
2009-04-24 3:20 ` Theodore Tso
2009-04-24 7:09 ` Andreas Dilger
2009-04-24 11:58 ` Theodore Tso
2009-04-24 20:09 ` Andreas Dilger
2009-04-24 8:57 ` Christian Kujau
2009-04-24 9:40 ` Christian Kujau
2009-04-24 12:00 ` Theodore Tso
2009-04-24 12:36 ` Eric Sandeen
2009-04-24 12:42 ` Eric Sandeen
2009-04-24 20:21 ` Christian Kujau
2009-04-24 20:34 ` Eric Sandeen
2009-04-24 20:59 ` Theodore Tso
2009-04-24 22:54 ` [PATCH] ext4: Do not try to validate extents on special files Theodore Ts'o
2009-04-24 21:02 ` ext4_ext_check_inode: bad header/extent in inode Christian Kujau
2009-04-24 21:23 ` Eric Sandeen [this message]
2009-04-24 20:41 ` Christian Kujau
2009-04-23 20:51 ` Andreas Dilger
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=49F22DC1.4080700@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=lists@nerdbynature.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.