archive mirror
 help / color / mirror / Atom feed
Subject: Re: New set of code snapshots for ext3-dxdir (kernel and userspace)
Date: Tue, 1 Oct 2002 04:21:51 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>; from on Tue, Oct 01, 2002 at 12:09:43AM -0400

On Tue, Oct 01, 2002 at 12:09:43AM -0400, wrote:
> Anyway, let's try to synchronize on a common set of kernel patches and
> userspace utilities, and see whether or not we've managed to get all of
> the problems fixed.

Sure, I'm willing (backed up my workstation completely, of course). I
first rebuilt 2.4.19 with your new patch applied on a ext3 fs with
dir_index disabled, built your new e2fsprogs WIP packages, and installed
them. Installed the new kernel. Turned on dir_index, and rebooted into
the new kernel.

> With these code base, and using a freshly created filesystem, I haven't
> been able to reproduce any problems using Ryan's fs-ream.c stress
> tester.  So I'm pretty confident about its stability, although there
> might possibly be some race conditions lurking about under extreme load.

Good news: I haven't been able to replicate any of the corruption I was
seeing earlier with Galeon 1.2.6 and Mozilla 1.1 from Debian's unstable
branch. This corruption would occur pretty randomly but almost
immediately after starting Galeon, and it'd show up immediately in my
xconsole (I use xdm) in the form of some nasty EXT3 errors (as I noted

I'll bang away with dump and bonnie[++] and see if I can make it spew.

Thanks again!


Dan Chen      
GPG key:

      reply	other threads:[~2002-10-01 11:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-01  4:09 New set of code snapshots for ext3-dxdir (kernel and userspace) tytso
2002-10-01 11:21 ` crimsun [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

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