Messages in this thread | | | Subject | [ANNOUNCE] Journaled File System (JFS) release 1.0.20 | From | "Steve Best" <> | Date | Fri, 21 Jun 2002 13:31:29 -0500 |
| |
Release 1.0.20 of JFS was made available today.
Drop 58 on June 21, 2002 (jfs-2.4-1.0.20.tar.gz and jfsutils-1.0.20.tar.gz) includes fixes to the file system and utilities.
Utilities changes
- don't display heartbeat during log format if output is redirected (eliminates strange characters in redirected output from mkfs.jfs with external log, fsck.jfs Phase 9) - fix mkfs.jfs to set version in JFS superblock properly if external log is used (enables JFS external log compatibility with EVMS 1.1-pre2 or greater) - enhance jfsutils to support enormous disks like 8TB+ (Peter C.) - remove unused variables (Christoph Hellwig)
File System changes
- set s_maxbytes to 1 byte lower When i_size was (PAGE_CACHE_SIZE << 32), generic_file_read overflowed an index and failed on any read. Subtracting one fixes it. - procfs entries should be created when CONFIG_JFS_STATISTICS is set. Currently, if CONFIG_JFS_DEBUG is not set, no entries are created under /proc/fs/jfs, even if CONFIG_JFS_STATISTICS is set. - fix fsync (Christoph Hellwig) fsync is allowed to return early if datasysnc is set and the I_DIRTY_DATASYNC flags is cleared, not if either of those is true - JFS does not need to set i_version. It is never used. (Manfred Spraul) - Fix for truncate problem, assert(!test_cflag(COMMIT_Nolink, ip)) kernel BUG at jfs_txnmgr.c537! (bugzilla #583) - Fix race in JFS kernel threads. Timing window existed between time threads dropped locks and slept, where the waker can try and wake the threads before they got to sleep.
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/
| |