Date:   Thu, 14 Oct 1999 20:10:54 +0100
From: "Stephen C. Tweedie" <sct@redhat.com>
To: linux-fsdevel@vger.rutgers.edu
Subject: Announce: ext2+journaling, release 0.0.2

Hi all,

OK, a couple of weeks later than I'd hoped and massive numbers of
bug-fixes further on, ext3-0.0.2 is out.  

This is the first usable release.  Apart from the critical failure
handling (handling of IO errors or memory allocation failures), this is
the first solid version of journaled ext2.  

The on-disk format is not yet finalised: there will be format changes to
the journal in the future, but you will always have an upgrade migration
path involving backing off from ext3 and then re-upgrading to the new
ext3.  So go out and hammer on it.  (No, *not* on your production web
server --- not just yet!)

Find it at

	ftp://ftp.uk.linux.org/pub/linux/sct/fs/jfs/ext3-0.0.2.tar.gz

Cheers,
 Stephen

----------------------------------------------------------------

Changes in this release
-----------------------

Bug fixes.  Lots of bug fixes.  Buckets of them.

It works on >1K blocksize filesystems.  It recovers reliably.  It
survives log wraps properly during recovery.  mknod() works properly: it
will no longer turn /dev into a socket if used on your root filesystem.  

This one survives under load quite happily.  A 50-client dbench run
completes reliably.

So basically, this is the first usable ext3 release.

Note that there are two major places where the implementation is not
complete: clean handling of all errors (in particular out-of-memory and
IO errors), and performance (there is still a lot of debugging code in
place, and all data is journaled as part of the testing cycle).  But it
is usable: I've been running it on all of my laptop's filesystems for
over a week now.