ext3 0.0.7a reviewDownload
ext3 adds journaling filesystem capabilities to ext2fs. What is journaling? It means you don't have to fsck after a crash
ext3 adds journaling filesystem capabilities to ext2fs.
What is journaling?
It means you don't have to fsck after a crash. Basically.
Journaling to a journal file on the journaled filesystem
Automatic recover when the filesystem is remounted
All VFS operations (including quota) should be journaled
Add data updates are also journaled
What is left to be done?
Quota support for non-data-journaled filesystems.
Journaling to an off-filesystem device, eg. NVRam
A few internal cleanups: migrating the extra buffer_head fields to a separate jfs_buffer_info field in particular.
What's New in This Release:
The major change in this release is a missing byte-endian conversion in the recovery code. This problem affects both the ext3 kernel recovery and the recovery code in e2fsck. Please upgrade to e2fsprogs-1.21-WIP-0601.tar.gz or later.
The other significant change is a fix when running shared mmaped files on ext3 with more than one ext3 filesystem active: it was possible for ext3 to get confused about which filesystem was active if the VM tried to swap out a page on one filesystem while processing a filesystem update on the other filesystem.
Pin the buffer heads backing an inode to a transaction when the transaction starts, to prevent the inode being flushed to disk before transaction commit.
Add a debugging check to trap any attempts to run a nested transaction inside a transaction on a different filesystem.
Fix an assertion failure that could occur after allocating an indirect block but failing to allocate a block beneath it due to disk full.
Fix a bug which meant that writes larger than 4k were never being coalesced into a single transaction.
Rename the confusingly-named "tid_ge" transaction-greater-than function to "tid_gt"
Update the README to describe the new ext3 features of current e2fsprogs.
ext3 0.0.7a keywords