Date: Thu, 13 Nov 2003 12:38:47 +0100
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)
Message-ID: <20031113113847.GX643@openzaurus.ucw.cz>
References: <20031108063341.GA8349@work.bitmover.com> <20031108164410.GB2955@thunk.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20031108164410.GB2955@thunk.org>
User-Agent: Mutt/1.3.27i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1215
Lines: 30

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...

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/