os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Whitespace-only fixes, translators please ignore.

Browse source
This commit is contained in:
Warren Block 2014-01-30 03:12:24 +00:00
parent 8a4ddc9b49
commit a743a631d7
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=43686
1 changed files with 112 additions and 48 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

160
en_US.ISO8859-1/books/handbook/geom/chapter.xml
View file

@ -4,15 +4,24 @@
$FreeBSD$
-->
<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="geom">
<info><title>GEOM: Modular Disk Transformation Framework</title>
<chapter xmlns="http://docbook.org/ns/docbook"
xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0"
xml:id="geom">
<info>
<title>GEOM: Modular Disk Transformation Framework</title>
<authorgroup>
<author><personname><firstname>Tom</firstname><surname>Rhodes</surname></personname><contrib>Written by </contrib></author>
<author>
<personname>
<firstname>Tom</firstname>
<surname>Rhodes</surname>
</personname>
<contrib>Written by </contrib>
</author>
</authorgroup>
</info>
<sect1 xml:id="geom-synopsis">
<title>Synopsis</title>
@ -25,7 +34,8 @@
</indexterm>
<para>This chapter covers the use of disks under the GEOM
framework in &os;. This includes the major <acronym role="Redundant Array of Inexpensive Disks">RAID</acronym>
framework in &os;. This includes the major <acronym
role="Redundant Array of Inexpensive Disks">RAID</acronym>
control utilities which use the framework for configuration.
This chapter will not go into in depth discussion on how GEOM
handles or controls I/O, the underlying subsystem, or code.
@ -64,11 +74,13 @@
<itemizedlist>
<listitem>
<para>Understand how &os; treats <link linkend="disks">disk devices</link>.</para>
<para>Understand how &os; treats <link linkend="disks">disk
devices</link>.</para>
</listitem>
<listitem>
<para>Know how to configure and install a new <link linkend="kernelconfig">&os; kernel</link>.</para>
<para>Know how to configure and install a new
<link linkend="kernelconfig">&os; kernel</link>.</para>
</listitem>
</itemizedlist>
</sect1>
@ -78,22 +90,34 @@
<para>GEOM permits access and control to classes, such as Master
Boot Records and <acronym>BSD</acronym> labels, through the use
of providers, or the special files in <filename>/dev</filename>. By supporting various
software <acronym>RAID</acronym> configurations, GEOM
transparently provides access to the operating system and
operating system utilities.</para>
of providers, or the special files in <filename>/dev</filename>.
By supporting various software <acronym>RAID</acronym>
configurations, GEOM transparently provides access to the
operating system and operating system utilities.</para>
</sect1>
<sect1 xml:id="geom-striping">
<info><title>RAID0 - Striping</title>
<info>
<title>RAID0 - Striping</title>
<authorgroup>
<author><personname><firstname>Tom</firstname><surname>Rhodes</surname></personname><contrib>Written by </contrib></author>
<author><personname><firstname>Murray</firstname><surname>Stokely</surname></personname></author>
<author>
<personname>
<firstname>Tom</firstname>
<surname>Rhodes</surname>
</personname>
<contrib>Written by </contrib>
</author>
<author>
<personname>
<firstname>Murray</firstname>
<surname>Stokely</surname>
</personname>
</author>
</authorgroup>
</info>
<indexterm>
<primary>GEOM</primary>
</indexterm>
@ -142,7 +166,8 @@
<step>
<para>Ensure that a suitable mount point exists. If this
volume will become a root partition, then temporarily use
another mount point such as <filename>/mnt</filename>:</para>
another mount point such as
<filename>/mnt</filename>:</para>
<screen>&prompt.root; <userinput>mkdir /mnt</userinput></screen>
</step>
@ -192,8 +217,9 @@ Done.</screen>
<para>To mount this striped file system automatically during the
boot process, place the volume information in
<filename>/etc/fstab</filename>. In this example, a
permanent mount point, named <filename>stripe</filename>, is created:</para>
<filename>/etc/fstab</filename>. In this example, a permanent
mount point, named <filename>stripe</filename>, is
created:</para>
<screen>&prompt.root; <userinput>mkdir /stripe</userinput>
&prompt.root; <userinput>echo "/dev/stripe/st0a /stripe ufs rw 2 2" \</userinput>
@ -407,7 +433,8 @@ Done.</screen>
are identical, it does not matter which is selected to
boot.</para>
<para>See the <link linkend="gmirror-troubleshooting">Troubleshooting</link>
<para>See the <link
linkend="gmirror-troubleshooting">Troubleshooting</link>
section if there are problems booting. Powering down and
disconnecting the original <filename>ada0</filename> disk
will allow it to be kept as an offline backup.</para>
@ -789,9 +816,11 @@ mountroot&gt;</screen>
<screen>&prompt.root; <userinput>gmirror forget gm0</userinput></screen>
<para>Any old metadata should be <link linkend="geom-mirror-metadata">cleared from the replacement
disk</link>. Then the disk, <filename>ada4</filename>
for this example, is inserted into the mirror:</para>
<para>Any old metadata should be
<link linkend="geom-mirror-metadata">cleared from the
replacement disk</link>. Then the disk,
<filename>ada4</filename> for this example, is inserted into
the mirror:</para>
<screen>&prompt.root; <userinput>gmirror insert gm0 /dev/ada4</userinput></screen>
@ -812,12 +841,19 @@ mountroot&gt;</screen>
</sect1>
<sect1 xml:id="geom-graid">
<info><title>Software <acronym>RAID</acronym> Devices</title>
<info>
<title>Software <acronym>RAID</acronym> Devices</title>
<authorgroup>
<author><personname><firstname>Warren</firstname><surname>Block</surname></personname><contrib>Originally contributed by </contrib></author>
<author>
<personname>
<firstname>Warren</firstname>
<surname>Block</surname>
</personname>
<contrib>Originally contributed by </contrib>
</author>
</authorgroup>
</info>
<indexterm>
<primary>GEOM</primary>
@ -1116,20 +1152,46 @@ raid/r0 OPTIMAL ada0 (ACTIVE (ACTIVE))
</sect1>
<sect1 xml:id="geom-raid3">
<info><title><acronym>RAID</acronym>3 - Byte-level Striping with
Dedicated Parity</title>
<info>
<title><acronym>RAID</acronym>3 - Byte-level Striping with
Dedicated Parity</title>
<authorgroup>
<author><personname><firstname>Mark</firstname><surname>Gladman</surname></personname><contrib>Written by </contrib></author>
<author><personname><firstname>Daniel</firstname><surname>Gerzo</surname></personname></author>
<author>
<personname>
<firstname>Mark</firstname>
<surname>Gladman</surname>
</personname>
<contrib>Written by </contrib>
</author>
<author>
<personname>
<firstname>Daniel</firstname>
<surname>Gerzo</surname>
</personname>
</author>
</authorgroup>
<authorgroup>
<author><personname><firstname>Tom</firstname><surname>Rhodes</surname></personname><contrib>Based on documentation by </contrib></author>
<author><personname><firstname>Murray</firstname><surname>Stokely</surname></personname></author>
<author>
<personname>
<firstname>Tom</firstname>
<surname>Rhodes</surname>
</personname>
<contrib>Based on documentation by </contrib>
</author>
<author>
<personname>
<firstname>Murray</firstname>
<surname>Stokely</surname>
</personname>
</author>
</authorgroup>
</info>
<indexterm>
<primary>GEOM</primary>
</indexterm>
@ -1294,7 +1356,8 @@ Done.</screen>
ggate0
&prompt.root; <userinput>mount /dev/ggate0 /mnt</userinput></screen>
<para>The device may now be accessed through the <filename>/mnt</filename> mount point.</para>
<para>The device may now be accessed through the
<filename>/mnt</filename> mount point.</para>
<note>
<para>However, this will fail if the device is currently mounted
@ -1362,18 +1425,18 @@ ggate0
<para>Permanent labels can be a generic or a file system label.
Permanent file system labels can be created with
&man.tunefs.8; or &man.newfs.8;. These types of labels are
created in a sub-directory of <filename>/dev</filename>, and will be named
according to the file system type. For example,
created in a sub-directory of <filename>/dev</filename>, and
will be named according to the file system type. For example,
<acronym>UFS</acronym>2 file system labels will be created in
<filename>/dev/ufs</filename>. Generic
permanent labels can be created with <command>glabel
label</command>. These are not file system specific and
will be created in <filename>/dev/label</filename>.</para>
<filename>/dev/ufs</filename>. Generic permanent labels can
be created with <command>glabel label</command>. These are
not file system specific and will be created in
<filename>/dev/label</filename>.</para>
<para>Temporary labels are destroyed at the next reboot. These
labels are created in <filename>/dev/label</filename> and are suited to
experimentation. A temporary label can be created using
<command>glabel create</command>.</para>
labels are created in <filename>/dev/label</filename> and are
suited to experimentation. A temporary label can be created
using <command>glabel create</command>.</para>
<!-- XXXTR: How do you create a file system label without running newfs
or when there is no newfs (e.g.: cd9660)? -->
@ -1389,8 +1452,8 @@ ggate0
corruption.</para>
</warning>
<para>A label should now exist in <filename>/dev/ufs</filename> which may be added
to <filename>/etc/fstab</filename>:</para>
<para>A label should now exist in <filename>/dev/ufs</filename>
which may be added to <filename>/etc/fstab</filename>:</para>
<programlisting>/dev/ufs/home /home ufs rw 2 2</programlisting>
@ -1612,7 +1675,8 @@ ufsid/486b6fc16926168e N/A ad4s1f</screen>
<command>tunefs</command>.</para>
<para>It is also possible to journal the boot disk of a &os;
system. Refer to the article <link xlink:href="&url.articles.gjournal-desktop;">Implementing UFS
system. Refer to the article <link
xlink:href="&url.articles.gjournal-desktop;">Implementing UFS
Journaling on a Desktop PC</link> for detailed
instructions.</para>
</sect1>