linux-ext4 - Re: How to remove a corrupted dir in an ext4 FS?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20101025142937.GB16981@thunk.org>
Date:	Mon, 25 Oct 2010 10:29:37 -0400
From:	Ted Ts'o <tytso@....edu>
To:	Andreas Dilger <adilger.kernel@...ger.ca>
Cc:	Jesus Sanchez Melendro <melendro@...ra.es>,
	linux-ext4@...r.kernel.org
Subject: Re: How to remove a corrupted dir in an ext4 FS?

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
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html