JFS (file system)

HP-UX has another, different filesystem named JFS that is actually an OEM version of Veritas Software's VxFS.

In 1995, work began to enhance the file system to be more scalable and to support machines that had more than one processor.

[4] This release of sources also worked to form the basis of a re-port back to OS/2 of the open-source JFS.

In parallel with this effort, some of the JFS development team returned to the AIX Operating System Development Group in 1997 and started to move this new JFS source base to the AIX operating system.

[1][3] Early in 2008 there was speculation that IBM is no longer interested in maintaining JFS and thus it should not be used in production environments.

He went on to add that certain distributions expect a larger resource commitment from them and opt not to support the filesystem.

Because of high CPU usage and increased free space fragmentation, compression is not recommended for use other than on a single user workstation or off-line backup areas.

Applications such as relational databases which maintain data consistency themselves can use this option to largely eliminate filesystem overheads.

The second policy is to distribute unrelated data throughout the file system in an attempt to minimize free-space fragmentation.

The superblock maintains information about the entire file system and includes the following fields: In the Linux operating system, JFS is supported with the kernel module (since the kernel version 2.4.18pre9-ac4) and the complementary userspace utilities packaged under the name JFSutils.

Most Linux distributions support JFS unless it is specifically removed due to space restrictions, such as on live CDs.

[citation needed] According to benchmarks of the available filesystems for Linux, JFS is fast and reliable, with consistently good performance under different kinds of load.