From: Mike Snitzer <snitzer@gmail.com>
To: "Andries E. Brouwer" <Andries.Brouwer@cwi.nl>
Cc: linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: ext3 duplicate entries with readdir
Date: Tue, 3 Mar 2009 15:54:02 -0500 [thread overview]
Message-ID: <170fa0d20903031254l7070294cwfa45ffdcc63b24d9@mail.gmail.com> (raw)
In-Reply-To: <20090303200526.GA20236@ub>
On Tue, Mar 3, 2009 at 3:05 PM, Andries E. Brouwer
<Andries.Brouwer@cwi.nl> wrote:
> In a largish directory (21292 files) a scan using ext3 readdir
> found 21293 files, returning one entry twice.
>
> Google "ext3 readdir twice" gives me a handful of identical complaints.
> I see reports from 2002-2008.
> So, this is an old and well-known symptom but seemingly still not fixed,
> at least not in the kernel on this machine here.
> This report is for Fedora release 8 (Werewolf) with kernel 2.6.24.5.
>
> A 2002 post says "This is unfortunate, but the chances of our hitting
> this failure are relatively small".
>
> In http://www.redhat.com/archives/ext3-users/2008-August/msg00009.html
> tytso seems to understand what happens: a hash collision.
> But has this been fixed in the current tree?
Yes, it has been fixed, please see the following git commits:
6a897cf447a83c9c3fd1b85a1e525c02d6eada7d
8c9fa93d51123c5540762b1a9e1919d6f9c4af7c
Mike
next prev parent reply other threads:[~2009-03-03 20:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 20:05 Andries E. Brouwer
2009-03-03 20:54 ` Mike Snitzer [this message]
2009-03-03 21:51 ` Andries E. Brouwer
2009-03-04 1:57 ` Theodore Tso
2009-03-09 14:13 ` Goswin von Brederlow
2009-03-09 16:00 ` Eric Sandeen
2009-03-11 10:45 ` Goswin von Brederlow
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=170fa0d20903031254l7070294cwfa45ffdcc63b24d9@mail.gmail.com \
--to=snitzer@gmail.com \
--cc=Andries.Brouwer@cwi.nl \
--cc=linux-ext4@vger.kernel.org \
--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®