| 1 |
<html> |
| 2 |
<head> |
| 3 |
<title>What is HFS+</title> |
| 4 |
</head> |
| 5 |
<body> |
| 6 |
<h2>What is HFS+</h2> |
| 7 |
<p> |
| 8 |
HFS+ is the new Filesystem intodruced my Apple around MacOS8. |
| 9 |
It became necessary because its predecessor, HFS, had a fixed numer |
| 10 |
of blocks (2^16), and on large volumes theses block became very |
| 11 |
large, wasting a lot of space. HFS+ solves this problem and |
| 12 |
intodruces some new concepts like Unicode file names. |
| 13 |
</p><p> |
| 14 |
Detailed Documentation can be found in |
| 15 |
<a href="http://developer.apple.com/technotes/tn/tn1150.html" |
| 16 |
>Technote 1150 HFS+ Volume format</a> and in |
| 17 |
<a href="http://developer.apple.com/techpubs/macos8/Files/FileManager/filemanager.html" |
| 18 |
>File Manager</a>. |
| 19 |
</p><p> |
| 20 |
In contrast to unix-like file Systems, HFS+ (and HFS+) work like indexes |
| 21 |
in a database. As with databases The index is composed of keys structered |
| 22 |
in a B*-Tree. (A B*Tree is basically a n-ary tree located in nodes on a volume. |
| 23 |
This way acces to any file is pretty fast at the price of a complex |
| 24 |
insert / delete management. I migt provide some O(..) notation |
| 25 |
here but dont want to get blamed by some Theoritican :) . |
| 26 |
The B*-tree is composed of index nodes and leaf nodes. Index nodes |
| 27 |
contain ordered keys that point to deeper index- or leaf-nodes. |
| 28 |
Leaf nodes contain keys and associated file or folder records. |
| 29 |
The keys and records have variable length but an additional |
| 30 |
index at the end of every node allows indexed acces. |
| 31 |
</p><p> |
| 32 |
Apple places additional restrictions on the B*-Tree:<ul> |
| 33 |
<li> All leaf nodes are found a the same depth</li> |
| 34 |
<li> All nodes of the same depth are linked foreward and backward</li> |
| 35 |
<li> ... More I dont remember right now.</li> |
| 36 |
</ul> |
| 37 |
</p><p> |
| 38 |
The keys are composed of the unique id of the parent folder and |
| 39 |
the (specially encoded) unicode name of the file. The folder |
| 40 |
THREADS are needed to retrive the parent folder for a given |
| 41 |
folder id. Theese use an empty name and are simliar to the |
| 42 |
'.' directory in unix. |
| 43 |
</p><p> |
| 44 |
Files and the B*Trees themselfes are stored in forks. For files these |
| 45 |
are the Apple-like data- and resource-fork. With HFS+ every files |
| 46 |
may have up to 8 not continuos parts until the additional parts |
| 47 |
are found in the Extends record. This Extends record is used |
| 48 |
for the catalog file (fork) and other forks, too. So that theese |
| 49 |
have fixed record ids, too. |
| 50 |
</p> |
| 51 |
<pre> |
| 52 |
$Id: hfsp.html,v 1.1.1.1 2002/03/05 19:50:28 klaus Exp $ |
| 53 |
</pre> |
| 54 |
</body> |
| 55 |
</html> |