[ANNOUNCE] Journaled File System (JFS) release 1.0.18

Steve Best (sbest@us.ibm.com)
Fri, 24 May 2002 13:37:36 -0500


Release 1.0.18 of JFS was made available today.

Drop 56 on May 24, 2002 (jfs-2.4-1.0.18.tar.gz
and jfsutils-1.0.18.tar.gz) includes fixes to the file
system and utilities.

The new feature in this release is the capability to have the
log on and external device. The -j journal device option in
mkfs.jfs allows you to specify the external log device. The
utilities now require libuuid and this is packaged with
e2fsprogs-devel that ships with most distros.

Utilities changes

- add support for external log
- endian code cleanup
- fix typo in fsck.jfs help
- fix fsck.jfs bug on big endian machines

File System changes

- File truncate was not always enough space from the block map.
- Bring 2.4 code in line with 2.5 and various cleanups (Christoph Hellwig)
- JFS metapage changes (Christoph Hellwig)
use the bdev mapping instead of JFS-private device mapping/inode
add metapages to -> mp_list of the inode passed to __get_metpage
- Reduce number of return paths in dbAlloc to two. This is in preparation
for quota support. (Christoph Hellwig)
- External journal support
Add uuid to file system and journal
- Add additional debug code to help debug mysterious uncommitted anonymous
txns
- Add xtAppend
- Add lmLogFromat which is used to format the file system log
- Add extern for diExtendFS
- Increase number of transaction locks in JFS txnmgr
- Make license boilerplate uniform, update copyright dates
- No need to handle regular files in jfs_mknod (Christoph Hellwig)
- Remove register keyword (Christoph Hellwig)
- Simplify sync_metapage (Christoph Hellwig)

For more details about JFS, please see the patch instructions or
changelog.jfs
files.

Steve Best
Linux Technology Center
JFS for Linux http://oss.software.ibm.com/jfs

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/