[ANNOUNCE] JFS 1.1.2

[Dave Kleikamp]

Release 1.1.3 of JFS was made available today.

It is important that you update the JFS utilities if you are using the
2.6.0 kernel.  A recent change in the kernel changed the behavior of
the O_EXCL flag in an open call to a block device.  Older versions of
fsck.jfs may fail to replay the journal when a file system is mounted
read-only.  (This will be the case if the root file system is JFS.)

Drop 66 on September 5, 2003 includes fixes to the file system and
utilities.

Utilities changes

- jfs_fsck can now find external journal on evms release 2 volumes
- code cleanup: fsck messaging is much cleaner
- Don't right-justify when printing volume label
- jfs_fsck should return zero when replaying the journal is successful
- jfs_fsck should not require that the device is opened with O_EXCL

File System changes

- Fix compat.h so that compile does not break on unlikely and dump_stack
- jfs_lookup should check for bad inode returned by iget
- Prevent rare deadlock
- Fix compile problem with recent Redhat kernels
- Code cleanup suggested by static analysis tool
- Peformance improvement
- Use block device inode/mapping instead of direct_inode/direct_mapping
- Support for kernels older than 2.4.18 has been removed
- Fix resize errors
- Fix possible trap/data loss when fixing directory index table
- If unicode conversion fails, operation should fail
- Code cleanup: make error return codes negative
- add nointegrity mount option
- Merge xattr code.  This has been in the official kernel since 2.4.20
- jfs_write_super_lockfs should mark superblock clean

Note: The 2.4.23 and 2.6 kernel.org development kernels are kept up to 
date with the latest JFS code.  The file system updates available on 
the web site are only needed for maintaining earlier 2.4 kernels.

For more details about JFS, please see our website:
http://oss.software.ibm.com/jfs
-- 
David Kleikamp
IBM Linux Technology Center

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