|| ||"Steve Best" <email@example.com>|
|| ||[ANNOUNCE] Journaled File System (JFS) release 1.0.23|
|| ||Fri, 27 Sep 2002 14:06:53 -0500|
Release 1.0.23 of JFS was made available today.
Drop 61 on September 27, 2002 (jfs-2.4-1.0.23.tar.gz
and jfsutils-1.0.23.tar.gz) includes fixes to the file
system and utilities.
- print fsck.jfs start timestamp correctly in fsck.jfs log
- allow xchklog to run on a JFS file system with an external journal
- initialize program name in logdump properly
- code cleanup
File System changes
- Detect and fix invalid directory index values
The directory index values are the unique cookies used to resume
a readdir at the proper place. These are stored with each entry
in a directory. fsck.jfs does not currently validate these entries,
nor even create them when populating the lost+found directory.
This fix causes readdir to detect the invalid cookies, and generate
new ones, if possible.
- Fix problems with NFS
Don't complain when read_inode is called with a deleted inode. This
is normally done by revalidate.
readdir: Don't hold metadata page while calling filldir(). NFS's
filldir may call lookup() which could result in a hang.
- Fix off-by-one error in dbNextAG
In certain situations, dbNextAG set db_agpref to db_numag, is
one higher than the last valid value. This will eventually result
in a trap.
- Avoid parallel allocations within the same allocation group
When large files are writing in parallel, allocating the space for
these files within the same allocation group can cause severe
fragmentation of the files. By keeping track of open, growing files
within an allocation group, we can force other new allocations into
a different allocation group to avoid causing fragmentation.
- Fix test in lmLogFileSystem
- Remove assert(i < MAX_ACTIVE) when the external log can't be found.
- Remove excessive typedefs
For more details about JFS, please see the patch instructions or
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 firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/