Re: Removing bad fsck inode files

Michael Clark (michael@astrolog.net)
Tue, 02 Nov 1999 19:12:53 +1300


Tom,

The corruption has probably set the immutable flag on these files.

Have you tried: chattr -i *

~mc

> Hello,
>
> I recently caused a significant amount of corruption on a disk by writing a
> large amount of mpeg 4 frames onto a component disk of my raid array. My
> fault, no doubt.
>
> Anyway, I fsck'd the array and after a bunch of tweaking recovered most of
> the data and was able to replace from backup whatever was lost.
>
> However, during the fsck process I got a large number of files in
> lost+found. No surprise there, but many of them are corrupted enough not to
> be removable. As it stands now I have 13,000 files in lost+found that I
> can't rm as root, or chown, or chmod.
>
> [root@music lost+found]# rm -f \#10002*
> rm: cannot unlink `#1000262': Operation not permitted
> rm: cannot unlink `#1000265': Operation not permitted
> rm: cannot unlink `#1000271': Operation not permitted
>
> [root@music lost+found]# ls -l \#10002*
> s-wS-ws--t 1 33828 65439 4294967295 Sep 6 1926 #1000262
> prw-rwx-wT 1 38913 63096 0 Mar 19 2031 #1000265
> b-ws--Srwx 1 1555 21628 143, 213 Sep 3 1992 #1000271
>
> [root@music lost+found]# ls -l | head -10
> ls: #413345: File too large
> ls: #416417: File too large
> ls: #634865: File too large
> ls: #637937: File too large
> ls: #759141: File too large
> ls: #762213: File too large
> [etc]
> total 13423668387269
> s-wS-ws--t 1 33828 65439 4294967295 Sep 6 1926 #1000262
> prw-rwx-wT 1 38913 63096 0 Mar 19 2031 #1000265
> b-ws--Srwx 1 1555 21628 143, 213 Sep 3 1992 #1000271
> c--xrw-r-T 1 61591 18828 225, 154 Aug 14 1994 #1000327
> srwx--x-wx 1 38624 37087 4294967295 Nov 12 1954 #1000403
> cr-sr---w- 1 46820 46933 95, 98 Dec 17 2015 #1000407
> crwx-wsr-T 1 60239 54163 97, 8 Dec 26 1984 #1000412
> pr-x----wx 1 48999 51012 0 Oct 4 1982 #1000416
> sr-S-wSr-T 1 14223 56773 4294967295 Apr 18 1991 #1000418
> Broken pipe
>
> Does anyone have any suggestions as to how to remove these? fsck does not
> seem to have a problem with them.
>
> tom
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.rutgers.edu
> Please read the FAQ at http://www.tux.org/lkml/

-- 
mc <michael@astrolog.net>

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/