High Performance File System: Difference between revisions

Revision as of 02:51, 31 July 2020

Latest revision as of 16:37, 5 August 2024

(17 intermediate revisions by 16 users not shown)

Line 1:

{{Short description|Filesystem created for OS/2 operating system}}

{{distinguish|Hi Performance FileSystem}}

{{ref improve|date=August 2013}}

Line 7 ⟶ 8:

|introduction_os = [[OS/2 1.2]]

|introduction_date = {{Start date and age|1989|11}}

|partition_id = <ttcode>[[Partition type#PID_07h|0x07]]</ttcode> ([[Master Boot Record|MBR]])

|directory_struct = [[B+ tree]]

|file_struct = [[B+ tree]]

|bad_blocks_struct = [[B+List tree(abstract data type)|List]]

|max_filename_size = 255 characters

|max_files_no = Unlimited

|max_volume_size = 64 [[gibibytegigabyte|GiBGB]] (as implemented)<br/>2 [[tebibyteterabyte|TiBTB]] (theoretical)

| max_file_size = 7.682 [[gibibytegigabyte|GiBGB]]

|filename_character_set = DoubleSingle-byte from <ttcode>0x00200x20</ttcode> to <ttcode>0xFFFF0xFF</ttcode>

|dates_recorded = Access, Creation, Modified

|date_range =

Line 24 ⟶ 25:

|compression = No

|encryption = No

|OS = [[OS/2]], [[Windows NT]], [[Linux]], [[DragonFly BSD]], [[eComStation]], [[ArcaOS]]

}}

Line 31 ⟶ 32:

== Overview ==

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

*Support for [[Case Sensitivity|mixed case]] file names, in different [[code page]]s

*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)

Line 41 ⟶ 42:

*Root directory located at the midpoint, rather than at the beginning of the disk, for faster average access

HPFS also can keep 64 [[KibibyteKilobyte|KiBKB]] of [[Metadata (computing)|metadata]] ("[[extended attribute]]s") per file.

IBM offers two kinds of [[Installable File System|IFS]] drivers for this file system:

*The standard one with a cache limited to 2&nbsp;MiBMB

*''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<ref>{{cite web|title=Virtual Memory Problems under OS/2|url=http://www.os2voice.org/VNL/past_issues/VNL0708H/feature_3.html|publisher=www.os2voice.org|accessdateaccess-date=11 June 2015|archive-url=https://web.archive.org/web/20150924061927/http://www.os2voice.org/VNL/past_issues/VNL0708H/feature_3.html|archive-date=24 September 2015|url-status=dead}}</ref> and was implemented in 32-bit [[assembly language]]. HPFS386 is a [[Ring (computer security)|ring 0]] driver (allowing direct hardware access and direct interaction with the kernel) with built-in SMB networking properties that are usable by various server [[daemon (computing)|daemon]]s, whereas HPFS is a [[Ring 3 (computer security)|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 iswas contingent upon the company paying Microsoft a licensing fee for each copy sold. This was a result fromof the Microsoft and IBM collaboration that gave both IBM and Microsoft hadthe right to use Windows and OS/2 technology. Microsoft used HPFS in Windows NT.

Due to the Microsoft dependence, limited partition size, file size limit of 2&nbsp;GiBGB and the long disk-check times after a crash, IBM ported the [[journaling file system]], [[JFS (file system)|JFS]], to OS/2 as a substitute.

[[DOS]] and [[Linux]] support HPFS via third-party drivers. [[Windows NT]] versions 3.51 (4.0) and earlier had native support for HPFS.

== Native support under Windows ==

[[Windows 95]] and its successors [[Windows 98]] and [[Windows Me]] canhave readno andsupport writefor HPFS. only{{citation whenneeded mapped via a network share; they cannot read it from a local disk.span|date=May 2023|They listed the [[NTFS]] partitions of networked computers as "HPFS"}}, because NTFS and HPFS share the same [[Partition type|filesystem identification number]] in the partition table.

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

Line 78 ⟶ 79:

| author=Ray Duncan

| journal=Microsoft Systems Journal

|date=September 1989|volume=4:5

| issue=5

| pages=1–13

}}

Line 96 ⟶ 98:

| title=HPFS unter Windows NT 4.0

| author=Dieter Brors

| journal=cC't Magazin für Computertechnik (German)

| year=1997|volume=1

| pages=306

Line 106 ⟶ 108:

|work=The Graham Utilities for OS/2 - Version 2

|url-status=dead

|archiveurlarchive-url=https://web.archive.org/web/20060210154146/http://www.warpspeed.com.au/Products/OS2/GU/Manual/appg.htm

|archivedatearchive-date=2006-02-10

}}

* [https://archive.today/20130130020814/http://homepage2.nifty.com/bayer/hpfs_w2k.html%23English How to get Windows NT 4, Windows 2000, and Windows XP to read HPFS partitions]

{{Filesystem}}

{{OS/2}}

[[Category:Disk file systems]]

Line 119 ⟶ 122:

[[Category:OS/2 technology|High Performance File System]]

[[Category:Computer file systems]]

[[Category:SoftwareAssembly writtenlanguage primarily in assembly languagesoftware]]