From: <sentry21@cdslash.net>
To: "Richard B. Johnson" <root@chaos.analogic.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Weird ext2fs immortal directory bug
Date: Thu, 26 Jul 2001 11:04:48 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.30.0107261104220.18300-100000@spring.webconquest.com> (raw)
In-Reply-To: <Pine.LNX.3.95.1010726105812.16941A-100000@chaos.analogic.com>
> On Thu, 26 Jul 2001 sentry21@cdslash.net wrote:
> [SNIPPED...]
> >
> > 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 ->
> >
>
> Did you try..
> # rm -r lost+found
> # mklost+found
>
> Without 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
next prev parent reply other threads:[~2001-07-26 15:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-26 14:37 sentry21
2001-07-26 15:02 ` Richard B. Johnson
2001-07-26 15:04 ` sentry21 [this message]
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.0107261104220.18300-100000@spring.webconquest.com \
--to=sentry21@cdslash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
/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®