From: Ted Ts'o <tytso@mit.edu>
To: Andreas Dilger <adilger.kernel@dilger.ca>
Cc: Jesus Sanchez Melendro <melendro@terra.es>, linux-ext4@vger.kernel.org
Subject: Re: How to remove a corrupted dir in an ext4 FS?
Date: Mon, 25 Oct 2010 10:29:37 -0400 [thread overview]
Message-ID: <20101025142937.GB16981@thunk.org> (raw)
In-Reply-To: <062C162D-7D68-4C2A-A6E8-B51F771E88D3@dilger.ca>
On Mon, Oct 25, 2010 at 10:16:55PM +0800, Andreas Dilger wrote:
> On 2010-10-24, at 19:12, Jesus Sanchez Melendro wrote:
> > After a corruption in an ext4 filesystem, I've checked and moved to the
> > correct position all the files and dirs in lost+found, but one of the dirs is
> > corrupted.
> >
> > The "ls -l" command says:
> > d????????? ? ? ? ? ? /lost+found/#90116
> >
> > If I try to remove it with "rmdir" or "rm -rf" or "mv" or "unlink", all
> > commands say:
> > <command used>: failed to remove `#90116': Input/output error
> >
> > Running "fsck" says that the filesystem is OK.
> >
> > Is there a way to remove that corrupted dir?
>
> You can probably check "lsattr /lost+found/#90116" to see if either
> the "i" (immutable) or "a" (append-only) attribute is set. If yes,
> then running "chattr -i -a/lost+found/#90116" will remove those
> attributes, and it should be removable.
If it was an immutable or apppend-only attribute, it should have
resulted in a "Operation not permitted" error. I suspect the problem
may be an underlying disk error. You might want to check "dmesg", and
see if the hard drive is reporting I/O errors. It may very well be
that you have problems a lot more serious than just a corrupted file
system. If so, you might want to consider making an immediate backup
right away, and strongly consider replacing the hard drive if you find
I/O errors in your system logs.
- Ted
prev parent reply other threads:[~2010-10-25 14:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-24 11:12 How to remove a corrupted dir in an ext4 FS? Jesus Sanchez Melendro
2010-10-25 14:16 ` Andreas Dilger
2010-10-25 14:29 ` Ted Ts'o [this message]
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=20101025142937.GB16981@thunk.org \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=melendro@terra.es \
/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).