linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@arcor.de>
To: Andreas Dilger <adilger@clusterfs.com>
Cc: Andrew_Purtell@NAI.com, tytso@mit.edu, linux-kernel@vger.kernel.org
Subject: Re: two problems using EXT3 htrees
Date: Fri, 11 Oct 2002 01:34:49 +0200	[thread overview]
Message-ID: <E17zmpQ-0000JK-00@starship> (raw)
In-Reply-To: <20021010170317.GI3045@clusterfs.com>

On Thursday 10 October 2002 19:03, Andreas Dilger wrote:
> On Oct 10, 2002  15:08 +0200, Daniel Phillips wrote:
> > On Wednesday 09 October 2002 20:29, Andrew_Purtell@NAI.com wrote:
> > > I recently patched my 2.4.19 kernel with EXT3 dir_index support and tried
> > > it out on my 80GB EXT3 data partition...
> > 
> > Could you please provide a pointer to the patch you used?
> 
> A number of people have been getting this same bug under high load.  I
> believe they are using the patches from Ted, and/or BK extfs.bkbits.net.

OK, I've read through the patch and the original thread re this problem.
There are a few obvious things to try:

  - Does the problem come up when there is only one rsync running
    concurrently?  (If so, we have a SMP race.)

  - Is the behaviour the same before and after Ted's cleanups?  (Get
    the old version out of cvs...)

  - Does the problem manifest with Ext2?  (Somebody - me probably -
    has to dust off the Ext2 patch and add the new hash.)

-- 
Daniel

      parent reply	other threads:[~2002-10-10 23:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-09 18:29 two problems using EXT3 htrees Andrew_Purtell
2002-10-10 13:08 ` Daniel Phillips
2002-10-10 17:03   ` Andreas Dilger
2002-10-10 19:07     ` Daniel Phillips
2002-10-10 23:34     ` Daniel Phillips [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:
  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=E17zmpQ-0000JK-00@starship \
    --to=phillips@arcor.de \
    --cc=Andrew_Purtell@NAI.com \
    --cc=adilger@clusterfs.com \
    --cc=linux-kernel@vger.kernel.org \
    --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).