This articleneeds additional citations forverification. Please helpimprove this article byadding citations to reliable sources. Unsourced material may be challenged and removed. Find sources: "High Performance File System" – news ·newspapers ·books ·scholar ·JSTOR(August 2013) (Learn how and when to remove this message)

HPFS (High Performance File System) is afile system created specifically for theOS/2operating system to improve upon the limitations of theFAT file system. It was written byGordon Letwin and others atMicrosoft and added to OS/2 version1.2, at that time still a joint undertaking of Microsoft andIBM, and released in 1988.

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

• Support formixed case file names, in differentcode pages
• Support for long file names (255 characters as opposed to FAT's8.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
• Lessfragmentation 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 64KB ofmetadata ("extended attributes") per file.

IBM offers two kinds ofIFS 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^[1] and was implemented in 32-bitassembly language. HPFS386 is aring 0 driver (allowing direct hardware access and direct interaction with the kernel) with built-in SMB networking properties that are usable by various serverdaemons, whereas HPFS is aring 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 thejournaling file system,JFS, to OS/2 as a substitute.

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

Windows 95 and its successorsWindows 98 andWindows Me have no support for HPFS.They listed theNTFS partitions of networked computers as "HPFS"^{[citation needed]}, because NTFS and HPFS share the samefilesystem identification number in the partition table.

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

Windows NT 3.51 can also read and write from local HPFS formatted drives. Starting withWindows NT 4 the filesystem driverPINBALL.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 theFAT12 andFAT16 filesystems. However, since HPFS lacks ajournal, any recovery after an unexpected shutdown or other error state takes progressively longer as the filesystem grows. A utility such asCHKDSK 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.

• Comparison of file systems
• HPFS BPB

• Ray Duncan (September 1989)."Design goals and implementation of the new High Performance File System".Microsoft Systems Journal.4 (5):1–13.
• Bridges, Dan (November 1996)."Inside the High Performance File System - parts 1 to 6".Electronic Developer Magazine for OS/2. Vol. 4, no. 10. Retrieved2016-07-18.
• Dieter Brors (1997)."HPFS unter Windows NT 4.0".C't Magazin für Computertechnik (German).1: 306.
• Chris Graham."Appendix G — HPFS internals".The Graham Utilities for OS/2 - Version 2. Archived fromthe original on 2006-02-10.
• How to get Windows NT 4, Windows 2000, and Windows XP to read HPFS partitions

• Disk file systems
• File systems supported by the Linux kernel
• IBM file systems
• Windows disk file systems
• OS/2 technology
• Computer file systems
• Assembly language software

• Articles with short description
• Short description matches Wikidata
• Articles needing additional references from August 2013
• All articles needing additional references
• All articles with unsourced statements
• Articles with unsourced statements from May 2023