From: "Theodore Ts'o" <tytso@mit.edu>
To: Ryan Cumming <ryan@completely.kicks-ass.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BK PATCH] Add ext3 indexed directory (htree) support
Date: Thu, 26 Sep 2002 11:42:17 -0400 [thread overview]
Message-ID: <20020926154217.GA10551@think.thunk.org> (raw)
In-Reply-To: <200209260041.59855.ryan@completely.kicks-ass.org>
On Thu, Sep 26, 2002 at 12:41:54AM -0700, Ryan Cumming wrote:
> On September 25, 2002 22:57, Theodore Ts'o wrote:
> > On Wed, Sep 25, 2002 at 10:23:11PM -0700, Ryan Cumming wrote:
> > > It seems to be running stable now. Linux 2.4.19, UP Athlon, GCC 3.2.
> >
> > Just to humor me, can you try it with gcc 2.95.4? I just want to
> > eliminate one variable....
>
> Using GCC 2.95.4 seems to stabilize dir_index nicely, both before and after
> the hdparm -fD run. Only the kernel was recompiled with 2.95.4, I reused the
> original GCC 3.2 compiled e2fsprogs.
Hmm... I just tried biult 2.4.19 with the ext3 patch on my UP P3
machine, using GCC 3.2, and I wasn't able to replicate your problem.
(This was using Debian's gcc 3.2.1-0pre2 release from testing.)
What was the precise GCC 3.2 version you were using, and for what
architecture were you compiling for? As I recall P3 kernels should
run on Athlons, if memory serves me correctly. (I don't have any
Athlons at home, so if it's an Athlon-specific code generation bug,
I'll have problems replicating it.) Could you try compiling a kernel
for the P3 architecture using GCC 3.2, and see whether or not the
problem is there? This is just a shot in the dark, but....
- Ted
next prev parent reply other threads:[~2002-09-26 15:37 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-25 20:03 [BK PATCH] Add ext3 indexed directory (htree) support tytso
2002-09-25 20:34 ` Andreas Dilger
2002-09-25 20:41 ` Dave Jones
2002-09-25 21:08 ` Andreas Dilger
2002-09-25 21:34 ` Theodore Ts'o
2002-09-25 22:54 ` Jeff Garzik
2002-09-25 23:29 ` Theodore Ts'o
2002-09-25 23:45 ` Ryan Cumming
2002-09-26 3:27 ` Theodore Ts'o
2002-09-26 5:23 ` Ryan Cumming
2002-09-26 5:57 ` Theodore Ts'o
2002-09-26 6:22 ` Ryan Cumming
2002-09-26 14:05 ` Theodore Ts'o
2002-09-26 6:25 ` Ryan Cumming
2002-09-26 11:25 ` Daniel Egger
2002-09-26 7:41 ` Ryan Cumming
2002-09-26 13:23 ` Theodore Ts'o
2002-09-26 15:42 ` Theodore Ts'o [this message]
2002-09-26 19:08 ` Ryan Cumming
2002-09-26 19:51 ` Horst von Brand
2002-09-26 19:59 ` Ryan Cumming
2002-09-26 22:04 ` Theodore Ts'o
2002-09-26 22:53 ` Ryan Cumming
2002-09-26 23:57 ` Theodore Ts'o
2002-09-27 1:00 ` Ryan Cumming
2002-09-27 3:24 ` Theodore Ts'o
2002-09-27 4:12 ` Andreas Dilger
2002-09-27 7:55 ` Ryan Cumming
2002-09-28 1:20 ` Ryan Cumming
2002-09-28 1:46 ` Ryan Cumming
2002-09-28 14:13 ` Theodore Ts'o
2002-09-28 14:18 ` Theodore Ts'o
2002-09-28 22:35 ` Ryan Cumming
2002-09-28 17:27 ` [Ext2-devel] " Andreas Dilger
2002-09-28 18:43 ` chrisl
2002-09-28 19:45 ` chrisl
2002-09-28 22:30 ` Ryan Cumming
2002-09-29 7:03 ` [PATCH] fix htree dir corrupt after fsck -fD chrisl
2002-09-29 8:16 ` Ryan Cumming
2002-09-29 8:36 ` Ryan Cumming
2002-09-30 2:46 ` Ryan Cumming
2002-09-29 14:13 ` Theodore Ts'o
2002-09-25 23:31 ` [BK PATCH] Add ext3 indexed directory (htree) support Daniel Egger
2002-09-26 0:32 ` Randy.Dunlap
2002-09-26 0:50 ` Aaron Lehmann
2002-09-26 3:28 ` Theodore Ts'o
2002-10-02 9:11 tytso
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=20020926154217.GA10551@think.thunk.org \
--to=tytso@mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=ryan@completely.kicks-ass.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;
as well as URLs for NNTP newsgroup(s).