linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Goswin von Brederlow <goswin-v-b@web.de>
Cc: Theodore Tso <tytso@mit.edu>,
	"Andries E. Brouwer" <Andries.Brouwer@cwi.nl>,
	Mike Snitzer <snitzer@gmail.com>,
	linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: ext3 duplicate entries with readdir
Date: Mon, 09 Mar 2009 11:00:21 -0500	[thread overview]
Message-ID: <49B53D15.6080003@redhat.com> (raw)
In-Reply-To: <87vdqivl66.fsf@frosties.localdomain>

Goswin von Brederlow wrote:
> Theodore Tso <tytso@mit.edu> writes:
> 
>> On Tue, Mar 03, 2009 at 10:51:26PM +0100, Andries E. Brouwer wrote:
>>>> Yes, it has been fixed, please see the following git commits:
>>>>
>>>> 6a897cf447a83c9c3fd1b85a1e525c02d6eada7d
>>>> 8c9fa93d51123c5540762b1a9e1919d6f9c4af7c
>>> [On another machine, Ubuntu with 2.6.27-7-server still fails:
>>> % ../readdirtest
>>> expected 61005 files, but readdir reports 61006
>>> % rm *
>>> rm: cannot remove `59992': No such file or directory
>>> (where the same name occurs twice in the expansion of *).]
>> The patches were backported to 2.6.27 stable in 2.6.27.8.  So the
>> problem would expected to be still present in an 2.6.27.7 kernel.
>>
>> 	      	       	     	   	   - Ted
> 
> Does the bug also affect xfs? Because I see the problem there.

Completely different, and the wrong list for the question, really.

Please point me to the bug you filed for this problem on xfs, I'll look
into it (and when you do so please cc: the xfs list, and trim off the
current ext4-related recipients)

Thanks,

-Eric

  reply	other threads:[~2009-03-09 16:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090303200526.GA20236@ub>
2009-03-03 20:54 ` ext3 duplicate entries with readdir Mike Snitzer
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 [this message]
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=49B53D15.6080003@redhat.com \
    --to=sandeen@redhat.com \
    --cc=Andries.Brouwer@cwi.nl \
    --cc=goswin-v-b@web.de \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=snitzer@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).