public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <andrewm@uow.edu.au>
To: "P.A.M. van Dam" <nucleus@ramoth.xs4all.nl>
Cc: "Peter J. Braam" <braam@clusterfilesystem.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Ext3 kernel RPMS (2.4.5 & 2.2.19)
Date: Sun, 10 Jun 2001 02:24:46 +1000	[thread overview]
Message-ID: <3B224DCE.7FB8F722@uow.edu.au> (raw)
In-Reply-To: <Pine.LNX.4.33.0106081522340.1388-100000@lustre.clusterfilesystem.com>, <Pine.LNX.4.33.0106081522340.1388-100000@lustre.clusterfilesystem.com>; from Peter J. Braam on Fri, Jun 08, 2001 at 03:23:16PM -0600 <20010609181551.A26422@ladystrange.bluehorizon.nl>

"P.A.M. van Dam" wrote:
> 
> On Fri, Jun 08, 2001 at 03:23:16PM -0600, Peter J. Braam wrote:
> > Hi,
> >
> > Mostly for my own use, I prepared two kernel RPM's with Ext3 in them.
> >
> > Versions:
> > 2.2.19 + 0.0.7a
> > 2.4.5  + 0.0.6
> >
> > PLEASE USE THESE AT YOUR OWN RISK - THEY CONTAIN EXPERIMENTAL FILE SYSTEM
> > CODE.
> > - Peter J. Braam -
> > http://www.clusterfilesystem.com
> 
> Ext3 for 2.4 kernels. Great. It's probably been asked before, but where can I
> find the ext3 patch for the 2.4 kernels?

All the details are at http://www.uow.edu.au/~andrewm/linux/ext3/

Current status is "pretty solid".  Performance is good.
It's basically untested against LVM and RAID.  It can
deadlock under heavy load if you're using quotas.

Avoid those things and you shouldn't have any problems.

Porting it (back) over to -ac and fixing up the quota
problems is basically the next activity on the list.

-

  reply	other threads:[~2001-06-09 16:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-08 21:23 Ext3 kernel RPMS (2.4.5 & 2.2.19) Peter J. Braam
2001-06-09 16:15 ` P.A.M. van Dam
2001-06-09 16:24   ` Andrew Morton [this message]
2001-06-09 19:39   ` Peter J. Braam

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=3B224DCE.7FB8F722@uow.edu.au \
    --to=andrewm@uow.edu.au \
    --cc=braam@clusterfilesystem.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nucleus@ramoth.xs4all.nl \
    /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