High Performance File System

HPFS
File system; permissions	Yes (only in HPFS386)
Transparent; compression	No
Transparent; encryption	No
Other
Supported; operating systems	OS/2, Windows NT, Linux, DragonFly BSD, eComStation, ArcaOS

HPFS (High Performance File System) is a

1.2, at that time still a joint undertaking of Microsoft and IBM

, and released in 1988.

Overview

Compared with FAT, HPFS provided a number of additional capabilities:

Support for
mixed case file names, in different code pages

Support for long file names (255 characters as opposed to FAT's

8.3

naming scheme)

More efficient use of disk space (files are not stored using multiple-sector clusters but on a per-sector basis)

An internal architecture that keeps related items close to each other on the disk volume

Less fragmentation of data
Extent-based space allocation
Separate datestamps for last modification, last access, and creation (as opposed to last-modification-only datestamp in then-times implementations of FAT)
B+ tree structure for directories
Root directory located at the midpoint, rather than at the beginning of the disk, for faster average access

HPFS also can keep 64

extended attributes

") per file.

IBM offers two kinds of IFS drivers for this file system:

The standard one with a cache limited to 2 MB
HPFS386 provided with certain server versions of OS/2, or as added component for the server versions that did not come with it

HPFS386's cache is limited by the amount of available memory in OS/2's system memory arena

ring 3

driver. Thus, HPFS386 is faster than HPFS and highly optimized for server applications. It is also highly tunable by experienced administrators.

Though IBM still had rights to HPFS, its agreement with Microsoft to continue licensing the HPFS386 version was contingent upon the company paying Microsoft a licensing fee for each copy sold. This was a result of the Microsoft and IBM collaboration that gave both the right to use Windows and OS/2 technology.

Due to the Microsoft dependence, limited partition size, file size limit of 2 GB and the long disk-check times after a crash, IBM ported the journaling file system, JFS, to OS/2 as a substitute.

DOS and Linux support HPFS via third-party drivers. Windows NT versions 3.51 and earlier had native support for HPFS.

Native support under Windows

Windows 95 and its successors Windows 98 and Windows Me can read and write HPFS only when mapped via a network share; they cannot read it from a local disk. They listed the NTFS partitions of networked computers as "HPFS"^{[citation needed]}, because NTFS and HPFS share the same filesystem identification number in the partition table.

Windows NT 3.1 and 3.5 have native read/write support for local disks and can even be installed onto an HPFS partition.

Windows NT 4

the filesystem driver PINBALL.SYS enabling the read/write access is not shipped anymore. Later Windows versions do not ship with this driver. Note that this driver is limited to 4GB HPFS volumes.

Microsoft retained rights to OS/2 technologies, including the HPFS filesystem, after they ceased collaboration with IBM. Since Windows NT 3.1 was designed for more rigorous (enterprise-class) use than previous versions of Windows, it included support for HPFS (and NTFS) giving it a larger storage capacity than the

FAT16 filesystems. However, since HPFS lacks a journal, any recovery after an unexpected shutdown or other error state takes progressively longer as the filesystem grows. A utility such as CHKDSK

would need to scan each entry in the filesystem to ensure no errors are present, a problem which is vastly reduced on NTFS, which simply replays the journal.

References

^ "Virtual Memory Problems under OS/2". www.os2voice.org. Archived from the original on 24 September 2015. Retrieved 11 June 2015.

High Performance File System

Overview

Native support under Windows

See also

References

Further reading