Re: how to remove bad inodes after fsck?
dz@cs.unitn.it (Massimo Dal Zotto) writes:
Try using "debugfs". It will allow you to remove things that
are otherwise not removable.
> Hi,
>
> I can't remove some files left in /lost+found from fsck after a bad crash:
>
> # ls -lR /lost+found/
> /lost+found/:
> total 1723224935
> sr-sr-sr-- 1 27814 52588 4294967295 Feb 11 1943 #4624
> drwxr-xr-x 2 root root 1024 Dec 29 14:43 #67082
>
> /lost+found/#67082:
> total 1723224934
> sr-sr-sr-- 1 27814 52588 4294967295 Feb 11 1943 spool
>
> # rm -f /lost+found/\#4624 /lost+found/\#67082/spool
> rm: cannot unlink `/lost+found/#4624': Operation not permitted
> rm: cannot unlink `/lost+found/#67082/spool': Operation not permitted
>
> # lsattr /lost+found/\#4624 /lost+found/\#67082/spool
> lsattr: Inappropriate ioctl for device While reading flags on /lost+found/#4624
> lsattr: Inappropriate ioctl for device While reading flags on /lost+found/#67082/spool
>
> Any idea?
>
> --
> Massimo Dal Zotto
>
--
* For God so loved the world that He gave his only begotten Son, *
* that whoever believes in Him should not perish... John 3:16 *
Reply to: