From: "Stephen C. Tweedie" <sct@redhat.com>
To: ext3-users@redhat.com, ext2-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Stephen Tweedie <sct@redhat.com>, Andrew Morton <akpm@zip.com.au>,
Andreas Dilger <adilger@home.com>
Subject: Ext3-0.9.18 available
Date: Thu, 16 May 2002 17:56:37 +0100 [thread overview]
Message-ID: <ac0ogp$mou$2@main.gmane.org> (raw)
Hi,
ext3-0.9.18 is now available for 2.4.19-pre8. Some of the fixes in
this release are already in the 2.4.19-pre8, but there are some
important new fixes in the patch and users are encouraged to upgrade.
This release fixes all known outstanding bug reports.
The full patch against linux-2.4.19-pre8, and a tarball of the
individual fixes in this patch set, is now propagating to
ftp://ftp.*.kernel.org/pub/linux/kernel/people/sct/ext3/v2.4/
The full list of changes is included below.
Cheers,
Stephen
---
ChangeLog:
* Speed up MS_SYNC writes
* Set up kjournald to be parented under init properly
* config: ext3 is no longer experimental
* fix i_blocks getting inconsistent after disk full
* speed up fsyncs in non-journaled data modes a little
* don't consider ENOSPC a fatal error when allocating an inode
* fix LVM snapshot deadlock
* fix "dump corrupts filesystems" core VFS bug
* fix over-zealous ext3 complaint about locked buffers
* fix very rare buffer leak
* fix O_SYNC
* fix tiny race where a buffer could be written to disk too soon
next reply other threads:[~2002-05-16 16:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-16 16:56 Stephen C. Tweedie [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-16 16:56 Ext3-0.9.18 available Stephen C. Tweedie
2002-05-17 12:17 ` Tomas Szepe
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='ac0ogp$mou$2@main.gmane.org' \
--to=sct@redhat.com \
--cc=adilger@home.com \
--cc=akpm@zip.com.au \
--cc=ext2-devel@lists.sourceforge.net \
--cc=ext3-users@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.