1 |
neysx |
1.1 |
<?xml version='1.0' encoding="UTF-8"?> |
2 |
jkt |
1.3 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-filesystems.xml,v 1.2 2008/03/03 01:27:18 nightmorph Exp $ --> |
3 |
neysx |
1.1 |
<!DOCTYPE included SYSTEM "/dtd/guide.dtd"> |
4 |
|
|
|
5 |
|
|
<included> |
6 |
|
|
|
7 |
jkt |
1.3 |
<version>3</version> |
8 |
|
|
<date>2008-03-03</date> |
9 |
neysx |
1.1 |
|
10 |
|
|
<section id="filesystemsdesc"> |
11 |
|
|
<title>Filesystems</title> |
12 |
|
|
<body> |
13 |
|
|
|
14 |
|
|
<p test="contains('x86 Alpha',func:keyval('arch'))"> |
15 |
|
|
The Linux kernel supports various filesystems. We'll explain ext2, ext3, |
16 |
|
|
ReiserFS, XFS and JFS as these are the most commonly used filesystems on Linux |
17 |
|
|
systems. |
18 |
|
|
</p> |
19 |
|
|
|
20 |
|
|
<p test="func:keyval('arch')='IA64'"> |
21 |
|
|
The Linux kernel supports various filesystems. We'll explain vfat, ext2, ext3, |
22 |
|
|
ReiserFS, XFS and JFS as these are the most commonly used filesystems on Linux |
23 |
|
|
systems. |
24 |
|
|
</p> |
25 |
|
|
|
26 |
|
|
<p test="func:keyval('arch')='AMD64'"> |
27 |
|
|
Several filesystems are available. Some of them are found stable on the amd64 |
28 |
|
|
architecture, others aren't. The following filesystems are found to be stable: |
29 |
jkt |
1.3 |
ext2, ext3 and XFS. JFS and ResierFS may work but need more testing. If you're |
30 |
nightmorph |
1.2 |
really adventurous you can try the other filesystems. |
31 |
neysx |
1.1 |
</p> |
32 |
|
|
|
33 |
|
|
<p test="func:keyval('arch')='arm'"> |
34 |
|
|
Several filesystems are available. Some of them are found stable on the arm |
35 |
jkt |
1.3 |
architecture, others aren't. ext2 and ext3 are found to be stable. JFS, XFS and |
36 |
neysx |
1.1 |
ReiserFS may work but need more testing. If you're really adventurous you can |
37 |
nightmorph |
1.2 |
try the other filesystems. |
38 |
neysx |
1.1 |
</p> |
39 |
|
|
|
40 |
|
|
<p test="func:keyval('arch')='HPPA'"> |
41 |
|
|
Several filesystems are available. Ext2, ext3, XFS and reiserfs are found |
42 |
|
|
stable on the HPPA architecture. The others are very experimental. |
43 |
|
|
</p> |
44 |
|
|
|
45 |
|
|
<p test="func:keyval('arch')='MIPS'"> |
46 |
|
|
Several filesystems are available. ReiserFS, EXT2 and EXT3 are found stable on |
47 |
|
|
the MIPS architectures, others are experimental. |
48 |
|
|
</p> |
49 |
|
|
|
50 |
|
|
<p test="func:keyval('arch')='PPC'"> |
51 |
|
|
Several filesystems are available for use on the PowerPC architecture including |
52 |
|
|
ext2, ext3, ReiserFS and XFS, each with their strengths and faults. |
53 |
|
|
</p> |
54 |
|
|
|
55 |
|
|
<note test="func:keyval('arch')='PPC64'"> |
56 |
|
|
Several filesystems are available. ext2, ext3 and ReiserFS support is built in |
57 |
|
|
the Installation CD kernels. JFS and XFS support is available through kernel |
58 |
|
|
modules. |
59 |
|
|
</note> |
60 |
|
|
|
61 |
|
|
<p test="func:keyval('arch')='SPARC'"> |
62 |
|
|
Several filesystems are available, some are known to be stable on the |
63 |
|
|
SPARC architecture. Ext2 and ext3, for example, are known to work well. |
64 |
|
|
Alternate filesystems may not function correctly. |
65 |
|
|
</p> |
66 |
|
|
|
67 |
|
|
<note test="func:keyval('arch')='Alpha'"> |
68 |
|
|
<c>aboot</c> only supports booting from <b>ext2</b> and <b>ext3</b> |
69 |
|
|
partitions. |
70 |
|
|
</note> |
71 |
|
|
|
72 |
|
|
</body> |
73 |
|
|
<body> |
74 |
|
|
|
75 |
|
|
<p test="func:keyval('arch')='IA64'"> |
76 |
|
|
<b>vfat</b> is the MS-DOS filesystem, updated to allow long filenames. It is |
77 |
|
|
also the only filesystem type that the EFI firmware on ia64 systems |
78 |
|
|
understands. The boot partition on ia64 systems should always be vfat, but for |
79 |
|
|
your data partitions you should use one of the other filesystems listed below. |
80 |
|
|
</p> |
81 |
|
|
|
82 |
|
|
<p> |
83 |
|
|
<b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata |
84 |
|
|
journaling, which means that routine ext2 filesystem checks at startup time can |
85 |
|
|
be quite time-consuming. There is now quite a selection of newer-generation |
86 |
|
|
journaled filesystems that can be checked for consistency very quickly and are |
87 |
|
|
thus generally preferred over their non-journaled counterparts. Journaled |
88 |
|
|
filesystems prevent long delays when you boot your system and your filesystem |
89 |
|
|
happens to be in an inconsistent state. |
90 |
|
|
</p> |
91 |
|
|
|
92 |
|
|
<p> |
93 |
|
|
<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata |
94 |
|
|
journaling for fast recovery in addition to other enhanced journaling modes like |
95 |
|
|
full data and ordered data journaling. It uses an HTree index that enables high |
96 |
|
|
performance in almost all situations. In short, ext3 is a very good and reliable |
97 |
|
|
filesystem. Ext3 is the recommended all-purpose all-platform filesystem. |
98 |
|
|
</p> |
99 |
|
|
|
100 |
|
|
</body> |
101 |
|
|
<body test="not(func:keyval('arch')='SPARC')"> |
102 |
|
|
|
103 |
|
|
<p test="not(func:keyval('arch')='PPC')"> |
104 |
|
|
<b>JFS</b> is IBM's high-performance journaling filesystem. JFS is a light, |
105 |
|
|
fast and reliable B+tree-based filesystem with good performance in various |
106 |
|
|
conditions. |
107 |
|
|
</p> |
108 |
|
|
|
109 |
|
|
<p> |
110 |
|
|
<b>ReiserFS</b> is a B+tree-based journaled filesystem that has good overall |
111 |
|
|
performance, especially when dealing with many tiny files at the cost of more |
112 |
|
|
CPU cycles. ReiserFS appears to be less maintained than other filesystems. |
113 |
|
|
</p> |
114 |
|
|
|
115 |
|
|
<p> |
116 |
|
|
<b>XFS</b> is a filesystem with metadata journaling which comes with a robust |
117 |
|
|
feature-set and is optimized for scalability. XFS seems to be less forgiving to |
118 |
|
|
various hardware problems. |
119 |
|
|
</p> |
120 |
|
|
|
121 |
|
|
</body> |
122 |
|
|
</section> |
123 |
|
|
</included> |