Contents of /xml/htdocs/doc/en/handbook/hb-install-filesystems.xml

Parent Directory Parent Directory | Revision Log Revision Log

Revision 1.8 - (hide annotations) (download) (as text)
Sun Sep 4 14:34:01 2011 UTC (7 years ago) by swift
Branch: MAIN
Changes since 1.7: +10 -10 lines
File MIME type: application/xml
Bug #334167 - Update filesystem information for ext4 for the arm, ia64 and sparc architectures

1 neysx 1.1 <?xml version='1.0' encoding="UTF-8"?>
2 swift 1.8 <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-filesystems.xml,v 1.7 2011/08/22 17:18:23 swift Exp $ -->
3 neysx 1.1 <!DOCTYPE included SYSTEM "/dtd/guide.dtd">
5     <included>
7 swift 1.8 <version>6</version>
8     <date>2011-09-04</date>
9 neysx 1.1
10     <section id="filesystemsdesc">
11     <title>Filesystems</title>
12     <body>
14     <p test="contains('x86 Alpha',func:keyval('arch'))">
15 swift 1.7 The Linux kernel supports various filesystems. We'll explain ext2, ext3, ext4,
16 neysx 1.1 ReiserFS, XFS and JFS as these are the most commonly used filesystems on Linux
17     systems.
18     </p>
20     <p test="func:keyval('arch')='IA64'">
21     The Linux kernel supports various filesystems. We'll explain vfat, ext2, ext3,
22 swift 1.8 ext4, ReiserFS, XFS and JFS as these are the most commonly used filesystems on
23     Linux systems.
24 neysx 1.1 </p>
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 swift 1.7 ext2, ext3, ext4 and XFS. JFS and ReiserFS may work but need more testing. If
30     you're really adventurous you can try the other filesystems.
31 neysx 1.1 </p>
33     <p test="func:keyval('arch')='arm'">
34     Several filesystems are available. Some of them are found stable on the arm
35 swift 1.8 architecture, others aren't. ext2, ext3 and ext4 are found to be stable. JFS,
36     XFS and ReiserFS may work but need more testing. If you're really adventurous
37     you can try the other filesystems.
38 neysx 1.1 </p>
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>
45     <p test="func:keyval('arch')='MIPS'">
46 swift 1.7 Several filesystems are available. ReiserFS, EXT2, EXT3 and EXT4 are found
47     stable on the MIPS architectures, others are experimental.
48 neysx 1.1 </p>
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>
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>
61     <p test="func:keyval('arch')='SPARC'">
62     Several filesystems are available, some are known to be stable on the
63 swift 1.8 SPARC architecture. Ext2, ext3 and ext4, for example, are known to work well.
64 neysx 1.1 Alternate filesystems may not function correctly.
65     </p>
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>
72     </body>
73     <body>
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>
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 nightmorph 1.6 happens to be in an inconsistent state. If you intend to install Gentoo on a
90     very small disk (less than 4GB), then you'll need to tell ext2 to reserve enough
91     inodes when you create the filesystem by running <c>mke2fs -T small
92     /dev/&lt;device&gt;</c>.
93 neysx 1.1 </p>
95     <p>
96     <b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata
97     journaling for fast recovery in addition to other enhanced journaling modes like
98     full data and ordered data journaling. It uses an HTree index that enables high
99 nightmorph 1.6 performance in almost all situations. In short, ext3 is a very good and
100     reliable filesystem. Ext3 is the recommended all-purpose all-platform
101     filesystem. If you intend to install Gentoo on a very small disk (less than
102     4GB), then you'll need to tell ext3 to reserve enough inodes when you create the
103     filesystem by running <c>mke2fs -j -T small /dev/&lt;device&gt;</c>.
104 neysx 1.1 </p>
106 swift 1.8 <p test="contains('x86 Alpha MIPS AMD64 arm IA64 SPARC',func:keyval('arch'))">
107 swift 1.7 <b>ext4</b> is a filesystem created as a fork of ext3 bringing new features,
108     performance improvements and removal of size limits with moderate changes
109     to the on-disk format. It can span volumes up to 1 EB and with maximum file
110     size of 16 TB. Instead of the classic ext2/3 bitmap block allocation ext4 uses
111     <uri link="http://en.wikipedia.org/wiki/Extent_%28file_systems%29">extents</uri>,
112     which improve large file performance and reduce fragmentation. Ext4 also provides
113     more sophisticated block allocation algorithms (delayed allocation and multiblock
114     allocation) giving the filesystem driver more ways to optimise the layout of data
115     on the disk. The ext4 filesystem is a compromise between production-grade code
116     stability and the desire to introduce extensions to an almost decade old
117     filesystem.
118     </p>
120 neysx 1.1 </body>
121     <body test="not(func:keyval('arch')='SPARC')">
123     <p test="not(func:keyval('arch')='PPC')">
124     <b>JFS</b> is IBM's high-performance journaling filesystem. JFS is a light,
125     fast and reliable B+tree-based filesystem with good performance in various
126     conditions.
127     </p>
129     <p>
130     <b>ReiserFS</b> is a B+tree-based journaled filesystem that has good overall
131     performance, especially when dealing with many tiny files at the cost of more
132     CPU cycles. ReiserFS appears to be less maintained than other filesystems.
133     </p>
135     <p>
136     <b>XFS</b> is a filesystem with metadata journaling which comes with a robust
137     feature-set and is optimized for scalability. XFS seems to be less forgiving to
138     various hardware problems.
139     </p>
141     </body>
142     </section>
143     </included>

  ViewVC Help
Powered by ViewVC 1.1.20