Capitalize section titles per Chicago Manual of Style.

This commit is contained in:
Murray Stokely 2003-05-04 12:01:40 +00:00
parent 27ba1359ad
commit 48e7898744
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=16782

View file

@ -42,7 +42,7 @@
</authorgroup>
</sect1info>
<title>Disks are too small</title>
<title>Disks Are Too Small</title>
<indexterm><primary>Vinum</primary></indexterm>
<indexterm><primary>RAID</primary>
@ -64,7 +64,7 @@
</sect1>
<sect1 id="vinum-access-bottlenecks">
<title>Access bottlenecks</title>
<title>Access Bottlenecks</title>
<para>Modern systems frequently need to access data in a highly
concurrent manner. For example, large FTP or HTTP servers can
@ -141,7 +141,7 @@
<para>
<figure id="vinum-concat">
<title>Concatenated organization</title>
<title>Concatenated Organization</title>
<graphic fileref="vinum/vinum-concat">
</figure>
</para>
@ -179,14 +179,14 @@
<para>
<figure id="vinum-striped">
<title>Striped organization</title>
<title>Striped Organization</title>
<graphic fileref="vinum/vinum-striped">
</figure>
</para>
</sect1>
<sect1 id="vinum-data-integrity">
<title>Data integrity</title>
<title>Data Integrity</title>
<para>The final problem with current disks is that they are
unreliable. Although disk drive reliability has increased
@ -249,7 +249,7 @@
<para>
<figure id="vinum-raid5-org">
<title>RAID-5 organization</title>
<title>RAID-5 Organization</title>
<graphic fileref="vinum/vinum-raid5-org">
</figure>
</para>
@ -267,7 +267,7 @@
</sect1>
<sect1 id="vinum-objects">
<title>Vinum objects</title>
<title>Vinum Objects</title>
<para>In order to address these problems, Vinum implements a four-level
hierarchy of objects:</para>
@ -314,7 +314,7 @@
functionality required of Vinum.</para>
<sect2>
<title>Volume size considerations</title>
<title>Volume Size Considerations</title>
<para>Plexes can include multiple subdisks spread over all
drives in the Vinum configuration. As a result, the size of
@ -323,7 +323,7 @@
</sect2>
<sect2>
<title>Redundant data storage</title>
<title>Redundant Data Storage</title>
<para>Vinum implements mirroring by attaching multiple plexes to
a volume. Each plex is a representation of the data in a
volume. A volume may contain between one and eight
@ -339,7 +339,7 @@
</sect2>
<sect2>
<title>Performance issues</title>
<title>Performance Issues</title>
<para>Vinum implements both concatenation and striping at the
plex level:</para>
@ -360,7 +360,7 @@
</sect2>
<sect2>
<title>Which plex organization?</title>
<title>Which Plex Organization?</title>
<para>The version of Vinum supplied with FreeBSD &rel.current; implements
two kinds of plex:</para>
@ -397,7 +397,7 @@
and disadvantages of each plex organization.</para>
<table id="vinum-comparison">
<title>Vinum Plex organizations</title>
<title>Vinum Plex Organizations</title>
<tgroup cols="5">
<thead>
<row>
@ -434,7 +434,7 @@
</sect1>
<sect1 id="vinum-examples">
<title>Some examples</title>
<title>Some Examples</title>
<para>Vinum maintains a <emphasis>configuration
database</emphasis> which describes the objects known to an
@ -447,7 +447,7 @@
accurately restores the state of each Vinum object.</para>
<sect2>
<title>The configuration file</title>
<title>The Configuration File</title>
<para>The configuration file describes individual Vinum objects. The
definition of a simple volume might be:</para>
@ -525,7 +525,7 @@
<para>
<figure id="vinum-simple-vol">
<title>A simple Vinum volume</title>
<title>A Simple Vinum Volume</title>
<graphic fileref="vinum/vinum-simple-vol">
</figure>
</para>
@ -545,7 +545,7 @@
</sect2>
<sect2>
<title>Increased resilience: mirroring</title>
<title>Increased Resilience: Mirroring</title>
<para>The resilience of a volume can be increased by mirroring.
When laying out a mirrored volume, it is important to ensure
@ -593,7 +593,7 @@
<para>
<figure id="vinum-mirrored-vol">
<title>A mirrored Vinum volume</title>
<title>A Mirrored Vinum Volume</title>
<graphic fileref="vinum/vinum-mirrored-vol">
</figure>
</para>
@ -604,7 +604,7 @@
</sect2>
<sect2>
<title>Optimizing performance</title>
<title>Optimizing Performance</title>
<para>The mirrored volume in the previous example is more
resistant to failure than an unmirrored volume, but its
@ -660,7 +660,7 @@
<para>
<figure id="vinum-striped-vol">
<title>A striped Vinum volume</title>
<title>A Striped Vinum Volume</title>
<graphic fileref="vinum/vinum-striped-vol">
</figure>
</para>
@ -672,7 +672,7 @@
</sect2>
<sect2>
<title>Resilience and performance</title>
<title>Resilience and Performance</title>
<para><anchor id="vinum-resilience">With sufficient hardware, it
is possible to build volumes which show both increased
@ -704,7 +704,7 @@
<para>
<figure id="vinum-raid10-vol">
<title>A mirrored, striped Vinum volume</title>
<title>A Mirrored, Striped Vinum Volume</title>
<graphic fileref="vinum/vinum-raid10-vol">
</figure>
</para>
@ -712,7 +712,7 @@
</sect1>
<sect1 id="vinum-object-naming">
<title>Object naming</title>
<title>Object Naming</title>
<para>As described above, Vinum assigns default names to plexes
and subdisks, although they may be overridden. Overriding the
@ -872,7 +872,7 @@
32 characters long.</para>
<sect2>
<title>Creating file systems</title>
<title>Creating File Systems</title>
<para>Volumes appear to the system to be identical to disks,
with one exception. Unlike UNIX&trade; drives, Vinum does
@ -959,7 +959,7 @@ sd name bigraid.p0.s4 drive e plex bigraid.p0 state initializing len 4194304b dr
IDs.</para>
<sect3>
<title>Automatic startup</title>
<title>Automatic Startup</title>
<para>In order to start Vinum automatically when you boot the
system, ensure that you have the following line in your