![[LWN Logo]](/images/lcorner.png) |
|
![[Timeline]](/images/Included.png) |
Date: Tue, 13 Feb 2001 16:41:09 +0000
From: "Stephen C. Tweedie" <sct@redhat.com>
To: ext3-users@redhat.com, linux-fsdevel@vger.kernel.org
Subject: ext3-0.0.6a available
Hi,
ext3-0.0.6a has been uploaded to
ftp.uk.linux.org:/pub/linux/sct/fs/jfs/ext3-0.0.6a.tar.gz
and
ftp.*.kernel.org:/pub/linux/kernel/people/sct/ext3/ext3-0.0.6a.tar.gz
This version changes the way dirty buffers are marked to protect
against device drivers which might block in the ll_rw_block()
function. (Loop and lvm are examples.) It should also fix a rare but
persistent report of "buffer already locked" failures.
Other, more minor fixes include fixing the typo which reversed the
behaviour of ordered and writeback data modes in 0.0.5e, and a couple
of fixes for truncates to make sure that they commit to disk
atomically even when being split over multiple transactions.
Please use the e2fsprogs-WIP-0117 release for e2fsck with this ext3
release, available from
ftp://download.sourceforge.net/pub/sourceforge
Cheers,
Stephen.
------------------------------------------------------------
Changes in this release
-----------------------
0.0.6a:
Fix typo: ordered and writeback data modes were working the wrong way
around.
Rework the dirty buffer handling: dirty flags are now held in a
private
flag while buffers are journaled, so the block device mid-layers see
those buffers as clean and non-flushable.
Fix some truncate recovery problems: not all filesystem state was
being
flushed in large truncates when we had to split the truncate over
multiple transactions, so the on-disk inode might be slightly
inconsistent after a crash.
Clear the dirty bits when forgetting buffers (prevents aborted
truncates
from leaving behind zeroed-out indirect buffers).
{ For older changes, see the file CHANGES. }
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org