The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: wingc@engin.umich.edu (Christopher Allen Wing)
Cc: sentry21@cdslash.net, linux-kernel@vger.kernel.org
Subject: Re: Weird ext2fs immortal directory bug (all-in-one)
Date: Thu, 26 Jul 2001 18:25:47 +0100 (BST)	[thread overview]
Message-ID: <E15PotP-0004AG-00@the-village.bc.nu> (raw)
In-Reply-To: <Pine.LNX.4.33.0107261312450.6405-100000@bayarea.engin.umich.edu> from "Christopher Allen Wing" at Jul 26, 2001 01:21:01 PM

> I am assuming that the problem here was that fsck restored a lost inode to
> lost+found, but the inode had been corrupted and had the immutable bit
> set.

Which would actually be an fsck bug, since such an inode isnt legal and cant
be fixed by normal means
 

  reply	other threads:[~2001-07-26 17:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-26 14:37 Weird ext2fs immortal directory bug sentry21
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 [this message]
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

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=E15PotP-0004AG-00@the-village.bc.nu \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sentry21@cdslash.net \
    --cc=wingc@engin.umich.edu \
    /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