/[gentoo]/xml/htdocs/doc/en/handbook/hb-install-hppa-disk.xml
Gentoo

Diff of /xml/htdocs/doc/en/handbook/hb-install-hppa-disk.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.23 Revision 1.24
2<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> 2<!DOCTYPE sections SYSTEM "/dtd/book.dtd">
3 3
4<!-- The content of this document is licensed under the CC-BY-SA license --> 4<!-- The content of this document is licensed under the CC-BY-SA license -->
5<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> 5<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
6 6
7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-hppa-disk.xml,v 1.23 2007/06/26 07:07:27 nightmorph Exp $ --> 7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-hppa-disk.xml,v 1.24 2008/04/01 08:53:46 nightmorph Exp $ -->
8 8
9<sections> 9<sections>
10 10
11<version>8.1</version> 11<version>9.0</version>
12<date>2007-06-26</date> 12<date>2008-04-01</date>
13 13
14<section> 14<section>
15<title>Introduction to Block Devices</title> 15<title>Introduction to Block Devices</title>
16<subsection>
17<title>Block Devices</title>
18<body>
19 16
20<p>
21We'll take a good look at disk-oriented aspects of Gentoo Linux and Linux in
22general, including Linux filesystems, partitions and block devices. Then, once
23you're familiar with the ins and outs of disks and filesystems, you'll be
24guided through the process of setting up partitions and filesystems for your
25Gentoo Linux installation.
26</p>
27
28<p>
29To begin, we'll introduce <e>block devices</e>. The most famous block device is
30probably the one that represents the first SCSI HD in a Linux system, namely
31<path>/dev/sda</path>.
32</p>
33
34<p>
35The block devices above represent an abstract interface to the disk. User
36programs can use these block devices to interact with your disk without
37worrying about whether your drives are IDE, SCSI or something else. The program
38can simply address the storage on the disk as a bunch of contiguous,
39randomly-accessible 512-byte blocks.
40</p>
41
42</body>
43</subsection> 17<subsection>
18<include href="../hb-install-blockdevices.xml"/>
19</subsection>
20
44<subsection> 21<subsection>
45<title>Partitions and Slices</title> 22<title>Partitions and Slices</title>
46<body> 23<body>
47 24
48<p> 25<p>
189Otherwise read on to learn about the available filesystems... 166Otherwise read on to learn about the available filesystems...
190</p> 167</p>
191 168
192</body> 169</body>
193</subsection> 170</subsection>
194<subsection>
195<title>Filesystems?</title>
196<body>
197 171
198<p>
199Several filesystems are available. Ext2, ext3, XFS and reiserfs are found
200stable on the HPPA architecture. The others are very experimental.
201</p>
202
203<p>
204<b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata
205journaling, which means that routine ext2 filesystem checks at startup time can
206be quite time-consuming. There is now quite a selection of newer-generation
207journaled filesystems that can be checked for consistency very quickly and are
208thus generally preferred over their non-journaled counterparts. Journaled
209filesystems prevent long delays when you boot your system and your filesystem
210happens to be in an inconsistent state.
211</p>
212
213<p>
214<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata
215journaling for fast recovery in addition to other enhanced journaling modes like
216full data and ordered data journaling. It uses an HTree index that enables high
217performance in almost all situations. In short, ext3 is a very good and reliable
218filesystem.
219</p>
220
221<p>
222<b>ReiserFS</b> is a B+tree-based filesystem that has very good overall
223performance and greatly outperforms both ext2 and ext3 when dealing with small
224files (files less than 4k), often by a factor of 10x-15x. ReiserFS also scales
225extremely well and has metadata journaling. ReiserFS is solid and usable as
226both general-purpose filesystem and for extreme cases such as the creation of
227large filesystems, very large files and directories containing tens of
228thousands of small files.
229</p>
230
231<p>
232<b>XFS</b> is a filesystem with metadata journaling which comes with a robust
233feature-set and is optimized for scalability. We only recommend using this
234filesystem on Linux systems with high-end SCSI and/or fibre channel storage and
235an uninterruptible power supply. Because XFS aggressively caches in-transit data
236in RAM, improperly designed programs (those that don't take proper precautions
237when writing files to disk and there are quite a few of them) can lose a good
238deal of data if the system goes down unexpectedly.
239</p>
240
241<p>
242<b>JFS</b> is IBM's high-performance journaling filesystem. It has recently
243become production-ready and there hasn't been a sufficient track record to
244comment positively nor negatively on its general stability at this point.
245</p>
246
247</body>
248</subsection> 172<subsection>
173<include href="hb-install-filesystems.xml"/>
174</subsection>
175
249<subsection id="filesystems-apply"> 176<subsection id="filesystems-apply">
250<title>Applying a Filesystem to a Partition</title> 177<title>Applying a Filesystem to a Partition</title>
251<body> 178<body>
252 179
253<p> 180<p>

Legend:
Removed from v.1.23  
changed lines
  Added in v.1.24

  ViewVC Help
Powered by ViewVC 1.1.20