| Developer | Microsoft |
|---|---|
| Full name | High Performance File System |
| Introduced | November 1989 (OS/2 1.2) |
| Partition identifier | 0x07 (MBR) |
| Structures | |
| Directory contents | B+ tree |
| File allocation | B+ tree |
| Bad blocks | B+ tree |
| Limits | |
| Max file size | 2 GiB |
| Max number of files | Unlimited |
| Max filename length | 255 characters |
| Max volume size | 2 TiB |
| Allowed characters in filenames | Double-byte from 0x0020 to 0xFFFF |
| Features | |
| Dates recorded | Access, Creation, Modified |
| Forks | Yes |
| Attributes | Read-only, hidden, system, archive |
| File system permissions | Yes (only in HPFS386) |
| Transparent compression | No |
| Transparent encryption | No |
| Supported operating systems | OS/2, Windows NT, Linux, FreeBSD |
HPFS or High Performance File System is a file system created specifically for the OS/2 operating system to improve upon the limitations of the FAT file system. It was written by Gordon Letwin and others at Microsoft and added to OS/2 version 1.2, at that time still a joint undertaking of Microsoft and IBM.
Among its improvements are:
- support for mixed case file names, in different code pages
- support for long file names (256 characters as opposed to FAT's 8+3 characters)
- 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 FAT's one last modification datestamp)
- a B+ tree structure for directories
- root directory located at the mid-point, rather than beginning of the disk, for faster average access
HPFS also can keep 64 KiB of metadata ("extended attributes") per file.
IBM offers two kind of IFS drivers for this file system:
- the standard one with a cache limited to 2 MiB
- HPFS386 provided with the server versions of OS/2
HPFS386's cache is limited by the available memory and was implemented in assembler. Thus, HPFS386 is faster, but IBM is required to pay Microsoft for each copy sold. It is highly tunable by experienced administrators.
IBM had still had right over HPFS , but not HPFS386.This was a result from the Microsoft and IBM collaboration that both IBM and Microsoft had right to use Windows and OS/2 technology. Microsoft used HPFS in Windows NT.
Because of the Microsoft dependence 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.
Windows Native Support
Windows 95 and its successors Windows 98, Windows Me can read/write HPFS only when mapped via a network share, but cannot read it from a local disk. They listed the NTFS partitions of networked computers as "HPFS", 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. This is because NT was originally going to be a version of OS/2.
Windows NT 3.51 can also read and write from local HPFS formatted drives. However, Microsoft discouraged using HPFS in Windows NT 4 and in subsequent versions. Microsoft even removed the ability of NT 3.51 to format an HPFS file system. Starting with Windows NT 4 the filesystem driver pinball.sys enabling the read/write access is not included in a default installation anymore. Pinball.sys is included on the installation media for Windows 2000 and can be manually installed and used with some limitations.[citation needed] Later Windows versions do not ship with this driver.
Microsoft retained rights to OS/2 technologies, including the HPFS filesystem, after they ceased collaboration. 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 FAT 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 where the journal is simply replayed.
See also
Further reading
- Roy Duncan (September 1989). "Design goals and implementation of the new High Performance File System". Microsoft Systems Journal 4:5: 1–13. http://pages.cs.wisc.edu/~bolo/shipyard/hpfs.html.
- Bridges, Dan (1996). "Inside the High Performance File System". Significant Bits magazine. http://www.nondot.org/sabre/os/files/FileSystems/HPFS/.
- Dieter Brors (1997). "HPFS unter Windows NT 4.0". C't Magazin für Computertechnik (German) 1: 306. http://www.heise.de/ct/97/01/306/.
- Chris Graham. "Appendix G — HPFS internals". The Graham Utilities for OS/2 - Version 2. http://www.warpspeed.com.au./Products/OS2/GU/Manual/appg.htm.
- How to get Windows NT 4, Windows 2000, and Windows XP to read HPFS partitions
This entry is from Wikipedia, the leading user-contributed encyclopedia. It may not have been reviewed by professional editors (see full disclaimer)
