On 2014-07-13 02:13, Anton Aylward wrote:
On 07/12/2014 05:27 PM, Carlos E. R. wrote:
Ideas?
BTDT.
Huh? Ah: cer@Telcontar:~> wtf BTDT BTDT: been there, done that cer@Telcontar:~>
What you have is corrupted inodes. The 'ls' command is trying its best to interpret the random bit patterns of the inodes. Its mapping the random junk there into what *you* interpret as various status bit according to the manual page. But really they are just nonsense. That is why you cannot delete anything. It's all corrupt.
That /does/make sense.
It really doesn't matter what the 'T' and 't' attributes are, or the 'S' and 's' or even the 'r', 'w', and 'x' since this is all just random stuff.
Like I said, BTDT.
What I did was went in with a low level binary editor and cleared out the inodes. Difficult and hairy stuff. I think there are other tools now, over and above fsck.
That is, backup and format again the disk. I see no other way. Or ignore the files, as they seem to be small. Meaning that fsck is broken itself, too. :-/ -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)