From: "Steve Best" <sbest@us.ibm.com>
To: linux-kernel@vger.kernel.org
Subject: [ANNOUNCE] Journaled File System (JFS) release 1.0.18
Date: Fri, 24 May 2002 13:37:36 -0500 [thread overview]
Message-ID: <OFD7E93986.34A72BB5-ON85256BC3.00661BF9@pok.ibm.com> (raw)
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
reply other threads:[~2002-05-24 18:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=OFD7E93986.34A72BB5-ON85256BC3.00661BF9@pok.ibm.com \
--to=sbest@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).