Weird ext2fs immortal directory bug
Try lsattr ./#3147 and see if the i attribute is set. If so, then (as root) do chattr -i ./#3147 and try again to remove it.
Wayne
[email protected] on 07/26/2001 10:04:48 AM
To: "Richard B. Johnson" <[email protected]>
cc: [email protected] (bcc: Wayne Brown/Corporate/Altec)
Subject: Re: Weird ext2fs immortal directory bug
Quoted 10 lines · On Thu, 26 Jul 2001 [email protected] wrote:
[SNIPPED...]
Quoted 7 lines
Here's the problem(s) (or at least, the symptoms):
sentry21@Petra:1:/lost+found$ ls -l total 0 lr----S--- 1 52 12337 0 Nov 1 2022 #3147 ->
Quoted 7 lines
Did you try..
# rm -r lost+found # mklost+foundWithout knowing how to use the ext2fs tools, and not wanting to risk more damage, I tried this and it worked when I had such a crash-induced problem.
sentry21@Petra:1:/$ sudo rm -rf lost+found/ rm: cannot unlink `lost+found/#3147': Operation not permitted rm: cannot remove directory `lost+found': Directory not empty
Dang.
--Dan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Quoted 7 lines · On Thu, 26 Jul 2001 [email protected] wrote:
Try lsattr ./#3147 and see if the i attribute is set. If so, then (as root) do
chattr -i ./#3147 and try again to remove it.Wayne
If you try that from a shell, it may fail because '#' means "ignore everything thereafter", so you are trying to do muck with the directory. I think:
chattr -i ./\#3147 had ought to do it.
Cheers,
Dick Johnson
Penguin : Linux version 2.4.1 on an i686 machine (799.53 BogoMips).
I was going to compile a list of innovations that could be attributed to Microsoft. Once I realized that Ctrl-Alt-Del was handled in the BIOS, I found that there aren't any.