From: <sentry21@cdslash.net>
To: <linux-kernel@vger.kernel.org>
Subject: Weird ext2fs immortal directory bug
Date: Thu, 26 Jul 2001 10:37:21 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.30.0107261028000.18300-100000@spring.webconquest.com> (raw)
A long long time ago, I can still remember... My computer hosed itself
(power out as I recall), and then when it was coming back up and running
e2fsck, the power went out again - perhaps not the exact situation, but
suffice to say, init ended up running e2fsck on my drive, and filling
/lost+found/ with lots of garbage, most of which I needed.
I managed to easily clean it out, with one exception. And a friend
recently suggested posting it to this list. Can anyone here
explain what on earth is going on, and how to get rid of it?
Incidentally, it's been around since a custom-compiled 2.3.x (where x > 40
I believe), and has been impervious to my fixing ever since.
Also, I'm not subscribed, so please, any replies CC'ed to
dan@cdslash.net, I'd appreciate it.
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 ->
sentry21@Petra:0:/lost+found$ file \#3147/
#3147/: directory
sentry21@Petra:0:/lost+found$ rm -rf \#3147/
rm: cannot unlink `#3147': Permission denied
sentry21@Petra:1:/lost+found$ sudo rm -rf \#3147/
rm: cannot unlink `#3147': Operation not permitted
sentry21@Petra:1:/lost+found$ sudo chown sentry21.sentry21 \#3147/
chown: changing ownership of `#3147': Operation not permitted
sentry21@Petra:1:/lost+found$ cd \#3147/
sentry21@Petra:0:/lost+found/#3147$ ls
#3147@
sentry21@Petra:0:/lost+found/#3147$ cd \#3147/
sentry21@Petra:0:/lost+found/#3147/#3147$ ls
#3147@
sentry21@Petra:0:/lost+found/#3147/#3147$ cd
\#3147/#3147/#3147/#3147/#3147/#3147/#3147/#3147/
sentry21@Petra:0:/lost+found/#3147/#3147/#3147/#3147/#3147/#3147/#3147/#3147/#3147/#3147$ ls
#3147@
sentry21@Petra:0:/lost+found/#3147/#3147/#3147/#3147/#3147/#3147/#3147/#3147/#3147/#3147$ pwd
/lost+found/#3147/#3147/#3147/#3147/#3147/#3147/#3147/#3147/#3147/#3147
sentry21@Petra:0:/lost+found/#3147/#3147/#3147/#3147/#3147/#3147/#3147/#3147/#3147/#3147$ file \#3147/
#3147/: directory
Weird, ne? I -did- manage to make it -not rwxrwxrwx, suid, sgid, sticky,
and every other bloody FS flag you can stick on a directory (and lots you
can't), but it's still impervious to my sk|llz. It's not hurting anything,
but cron whines about it every day.
Thanks.
--Dan
next reply other threads:[~2001-07-26 14:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-26 14:37 sentry21 [this message]
2001-07-26 15:02 ` Richard B. Johnson
2001-07-26 15:04 ` sentry21
2001-07-26 15:32 ` Dan Podeanu
2001-07-26 15:37 ` sentry21
2001-07-26 15:48 ` Richard B. Johnson
2001-07-26 15:50 ` sentry21
2001-07-26 16:05 ` Richard B. Johnson
2001-07-26 16:10 ` Horst von Brand
2001-07-26 15:34 ` Sven Vermeulen
2001-07-26 15:44 ` Daniel Phillips
2001-07-26 17:08 ` Weird ext2fs immortal directory bug (all-in-one) sentry21
2001-07-26 17:21 ` Christopher Allen Wing
2001-07-26 17:25 ` Alan Cox
2001-07-26 18:21 ` Andreas Dilger
2001-07-26 19:11 ` Chris Meadors
2001-07-27 3:17 ` Gerhard Mack
2001-07-26 23:10 ` Andreas Dilger
2001-07-26 16:22 ` Weird ext2fs immortal directory bug Andreas Dilger
2001-07-26 16:02 Wayne.Brown
2001-07-26 16:52 ` Richard B. Johnson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.30.0107261028000.18300-100000@spring.webconquest.com \
--to=sentry21@cdslash.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®