All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: "Theodore Ts'o" <tytso@mit.edu>,
	Larry McVoy <lm@work.bitmover.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Weird ext2 problem in 2.4.18 (redhat)
Date: Thu, 13 Nov 2003 12:38:47 +0100	[thread overview]
Message-ID: <20031113113847.GX643@openzaurus.ucw.cz> (raw)
In-Reply-To: <20031108164410.GB2955@thunk.org>

Hi!

> > Hey, neato, it gets weirder.  I went to go run an example and now most of
> > the files in " src/" are gone, most but not all.
> 
> Sounds like there is a two directory entries with the same name in the
> same directory.  This can cuase severe confusion since the kernel
> assumes that this will never happen.  Depending on which one gets
> found first, and what is cached in the dentry cache, you'll get one
> inode or the other.
> 
> E2fsck doesn't normally notice these sorts of inconsistencies, since
> it takes too much time and memory to look for duplicate entries.  If
> you optimize directories using "e2fsck -fD", it will find and offer to
> rename directory entires with a duplicated name.

Is not that a little dangerous? I'd expect filesystem to be
okay after doing plain normal check.

What about at least documenting it in BUGS section of man
page?
-- 
				Pavel
Written on sharp zaurus, because my Velo1 broke. If you have Velo you don't need...


      parent reply	other threads:[~2003-11-13 11:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-08  6:33 Weird ext2 problem in 2.4.18 (redhat) Larry McVoy
2003-11-08 16:44 ` Theodore Ts'o
2003-11-08 20:03   ` Larry McVoy
2003-11-08 22:12   ` Davide Libenzi
2003-11-13 11:38   ` Pavel Machek [this message]

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=20031113113847.GX643@openzaurus.ucw.cz \
    --to=pavel@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@work.bitmover.com \
    --cc=tytso@mit.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.