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

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

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

Revision 1.24 Revision 1.25
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-mips-disk.xml,v 1.24 2007/06/26 07:07:27 nightmorph Exp $ --> 7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-mips-disk.xml,v 1.25 2008/04/01 08:53:46 nightmorph Exp $ -->
8 8
9<sections> 9<sections>
10 10
11<version>2.1</version> 11<version>3.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</title> 22<title>Partitions</title>
46<body> 23<body>
47 24
48<p> 25<p>
530read on to learn about the available filesystems... 507read on to learn about the available filesystems...
531</p> 508</p>
532 509
533</body> 510</body>
534</subsection> 511</subsection>
535<subsection>
536<title>Filesystems?</title>
537<body>
538 512
539<p>
540Several filesystems are available. ReiserFS, EXT2 and EXT3 are found stable on
541the MIPS architectures, others are experimental.
542</p>
543
544<p>
545<b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata
546journaling, which means that routine ext2 filesystem checks at startup time can
547be quite time-consuming. There is now quite a selection of newer-generation
548journaled filesystems that can be checked for consistency very quickly and are
549thus generally preferred over their non-journaled counterparts. Journaled
550filesystems prevent long delays when you boot your system and your filesystem
551happens to be in an inconsistent state.
552</p>
553
554<p>
555<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata
556journaling for fast recovery in addition to other enhanced journaling modes like
557full data and ordered data journaling. It uses an HTree index that enables high
558performance in almost all situations. In short, ext3 is a very good and reliable
559filesystem.
560</p>
561
562<p>
563<b>ReiserFS</b> is a B+tree-based filesystem that has very good overall
564performance and greatly outperforms both ext2 and ext3 when dealing with small
565files (files less than 4k), often by a factor of 10x-15x. ReiserFS also scales
566extremely well and has metadata journaling. ReiserFS is solid and usable as
567both general-purpose filesystem and for extreme cases such as the creation of
568large filesystems, very large files and directories containing tens of
569thousands of small files.
570</p>
571
572<p>
573<b>XFS</b> is a filesystem with metadata journaling which comes with a robust
574feature-set and is optimized for scalability. We only recommend using this
575filesystem on Linux systems with high-end SCSI and/or fibre channel storage and
576an uninterruptible power supply. Because XFS aggressively caches in-transit
577data in RAM, improperly designed programs (those that don't take proper
578precautions when writing files to disk and there are quite a few of them) can
579lose a good deal of data if the system goes down unexpectedly.
580</p>
581
582<p>
583<b>JFS</b> is IBM's high-performance journaling filesystem. It has recently
584become production-ready and there hasn't been a sufficient track record to
585comment positively nor negatively on its general stability at this point.
586</p>
587
588</body>
589</subsection> 513<subsection>
514<include href="hb-install-filesystems.xml"/>
515</subsection>
516
590<subsection id="filesystems-apply"> 517<subsection id="filesystems-apply">
591<title>Applying a Filesystem to a Partition</title> 518<title>Applying a Filesystem to a Partition</title>
592<body> 519<body>
593 520
594<p> 521<p>

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

  ViewVC Help
Powered by ViewVC 1.1.20