From: Andreas Dilger <adilger@clusterfs.com>
To: Daniel Phillips <phillips@arcor.de>
Cc: Andrew_Purtell@NAI.com, tytso@mit.edu, linux-kernel@vger.kernel.org
Subject: Re: two problems using EXT3 htrees
Date: Thu, 10 Oct 2002 11:03:17 -0600 [thread overview]
Message-ID: <20021010170317.GI3045@clusterfs.com> (raw)
In-Reply-To: <E17zd3i-0008A8-00@starship>
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.
Cheers, Andreas
--
Andreas Dilger
http://www-mddsp.enel.ucalgary.ca/People/adilger/
http://sourceforge.net/projects/ext2resize/
next prev parent reply other threads:[~2002-10-10 17:00 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 [this message]
2002-10-10 19:07 ` Daniel Phillips
2002-10-10 23:34 ` Daniel Phillips
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=20021010170317.GI3045@clusterfs.com \
--to=adilger@clusterfs.com \
--cc=Andrew_Purtell@NAI.com \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@arcor.de \
--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