diff options
Diffstat (limited to 'zh_TW.Big5/books/handbook/vinum/chapter.xml')
| -rw-r--r-- | zh_TW.Big5/books/handbook/vinum/chapter.xml | 98 |
1 files changed, 45 insertions, 53 deletions
diff --git a/zh_TW.Big5/books/handbook/vinum/chapter.xml b/zh_TW.Big5/books/handbook/vinum/chapter.xml index 1e8a1cc888..4d4e8cc7cd 100644 --- a/zh_TW.Big5/books/handbook/vinum/chapter.xml +++ b/zh_TW.Big5/books/handbook/vinum/chapter.xml @@ -10,21 +10,16 @@ $FreeBSD$ Original revision: 1.37 --> - -<chapter id="vinum-vinum"> - <chapterinfo> +<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="vinum-vinum"> + <info><title>The Vinum Volume Manager</title> <authorgroup> - <author> - <firstname>Greg</firstname> - <surname>Lehey</surname> - <contrib>Originally written by </contrib> - </author> + <author><personname><firstname>Greg</firstname><surname>Lehey</surname></personname><contrib>Originally written by </contrib></author> </authorgroup> - </chapterinfo> + </info> - <title>The Vinum Volume Manager</title> + - <sect1 id="vinum-synopsis"> + <sect1 xml:id="vinum-synopsis"> <title>Synopsis</title> @@ -59,7 +54,7 @@ disk storage, and an introduction to the Vinum Volume Manager.</para> </sect1> - <sect1 id="vinum-intro"> + <sect1 xml:id="vinum-intro"> <title>Disks Are Too Small</title> <indexterm><primary>Vinum</primary></indexterm> @@ -81,7 +76,7 @@ disk storage, and an introduction to the Vinum Volume Manager.</para> device which stores its data on a number of disks.</para> </sect1> - <sect1 id="vinum-access-bottlenecks"> + <sect1 xml:id="vinum-access-bottlenecks"> <title>Access Bottlenecks</title> <para>Modern systems frequently need to access data in a highly @@ -106,7 +101,7 @@ disk storage, and an introduction to the Vinum Volume Manager.</para> to be atomic: it does not make any sense to interrupt them.</para> - <para><anchor id="vinum-latency"/> Consider a typical transfer of + <para><anchor xml:id="vinum-latency"/> Consider a typical transfer of about 10 kB: the current generation of high-performance disks can position the heads in an average of 3.5 ms. The fastest drives spin at 15,000 rpm, so the average @@ -158,9 +153,9 @@ disk storage, and an introduction to the Vinum Volume Manager.</para> organization.</para> <para> - <figure id="vinum-concat"> + <figure xml:id="vinum-concat"> <title>Concatenated Organization</title> - <graphic fileref="vinum/vinum-concat"/> + <mediaobject><imageobject><imagedata fileref="vinum/vinum-concat"/></imageobject></mediaobject> </figure> </para> @@ -197,14 +192,14 @@ disk storage, and an introduction to the Vinum Volume Manager.</para> organization.</para> <para> - <figure id="vinum-striped"> + <figure xml:id="vinum-striped"> <title>Striped Organization</title> - <graphic fileref="vinum/vinum-striped"/> + <mediaobject><imageobject><imagedata fileref="vinum/vinum-striped"/></imageobject></mediaobject> </figure> </para> </sect1> - <sect1 id="vinum-data-integrity"> + <sect1 xml:id="vinum-data-integrity"> <title>Data Integrity</title> <para>The final problem with current disks is that they are @@ -267,9 +262,9 @@ disk storage, and an introduction to the Vinum Volume Manager.</para> blocks indicate the relative block numbers.</para> <para> - <figure id="vinum-raid5-org"> + <figure xml:id="vinum-raid5-org"> <title>RAID-5 Organization</title> - <graphic fileref="vinum/vinum-raid5-org"/> + <mediaobject><imageobject><imagedata fileref="vinum/vinum-raid5-org"/></imageobject></mediaobject> </figure> </para> @@ -285,7 +280,7 @@ disk storage, and an introduction to the Vinum Volume Manager.</para> </para> </sect1> - <sect1 id="vinum-objects"> + <sect1 xml:id="vinum-objects"> <title>Vinum Objects</title> <para>In order to address these problems, Vinum implements a four-level hierarchy of objects:</para> @@ -415,7 +410,7 @@ disk storage, and an introduction to the Vinum Volume Manager.</para> <para><xref linkend="vinum-comparison"/> summarizes the advantages and disadvantages of each plex organization.</para> - <table id="vinum-comparison" frame="none"> + <table xml:id="vinum-comparison" frame="none"> <title>Vinum Plex Organizations</title> <tgroup cols="5"> <thead> @@ -452,7 +447,7 @@ disk storage, and an introduction to the Vinum Volume Manager.</para> </sect2> </sect1> - <sect1 id="vinum-examples"> + <sect1 xml:id="vinum-examples"> <title>Some Examples</title> <para>Vinum maintains a <emphasis>configuration @@ -543,9 +538,9 @@ disk storage, and an introduction to the Vinum Volume Manager.</para> is represented graphically in <xref linkend="vinum-simple-vol"/>.</para> <para> - <figure id="vinum-simple-vol"> + <figure xml:id="vinum-simple-vol"> <title>A Simple Vinum Volume</title> - <graphic fileref="vinum/vinum-simple-vol"/> + <mediaobject><imageobject><imagedata fileref="vinum/vinum-simple-vol"/></imageobject></mediaobject> </figure> </para> @@ -611,9 +606,9 @@ disk storage, and an introduction to the Vinum Volume Manager.</para> graphically.</para> <para> - <figure id="vinum-mirrored-vol"> + <figure xml:id="vinum-mirrored-vol"> <title>A Mirrored Vinum Volume</title> - <graphic fileref="vinum/vinum-mirrored-vol"/> + <mediaobject><imageobject><imagedata fileref="vinum/vinum-mirrored-vol"/></imageobject></mediaobject> </figure> </para> @@ -678,9 +673,9 @@ disk storage, and an introduction to the Vinum Volume Manager.</para> S striped.p0.s3 State: up PO: 1536 kB Size: 128 MB</programlisting> <para> - <figure id="vinum-striped-vol"> + <figure xml:id="vinum-striped-vol"> <title>A Striped Vinum Volume</title> - <graphic fileref="vinum/vinum-striped-vol"/> + <mediaobject><imageobject><imagedata fileref="vinum/vinum-striped-vol"/></imageobject></mediaobject> </figure> </para> @@ -693,7 +688,7 @@ disk storage, and an introduction to the Vinum Volume Manager.</para> <sect2> <title>Resilience and Performance</title> - <para><anchor id="vinum-resilience"/>With sufficient hardware, it + <para><anchor xml:id="vinum-resilience"/>With sufficient hardware, it is possible to build volumes which show both increased resilience and increased performance compared to standard &unix; partitions. A typical configuration file might @@ -722,15 +717,15 @@ disk storage, and an introduction to the Vinum Volume Manager.</para> of this volume.</para> <para> - <figure id="vinum-raid10-vol"> + <figure xml:id="vinum-raid10-vol"> <title>A Mirrored, Striped Vinum Volume</title> - <graphic fileref="vinum/vinum-raid10-vol"/> + <mediaobject><imageobject><imagedata fileref="vinum/vinum-raid10-vol"/></imageobject></mediaobject> </figure> </para> </sect2> </sect1> - <sect1 id="vinum-object-naming"> + <sect1 xml:id="vinum-object-naming"> <title>Object Naming</title> <para>As described above, Vinum assigns default names to plexes @@ -902,10 +897,10 @@ disk storage, and an introduction to the Vinum Volume Manager.</para> partition identifier. For example, a disk drive may have a name like <filename>/dev/ad0a</filename> or <filename>/dev/da2h</filename>. These names represent - the first partition (<devicename>a</devicename>) on the - first (0) IDE disk (<devicename>ad</devicename>) and the - eighth partition (<devicename>h</devicename>) on the third - (2) SCSI disk (<devicename>da</devicename>) respectively. + the first partition (<filename>a</filename>) on the + first (0) IDE disk (<filename>ad</filename>) and the + eighth partition (<filename>h</filename>) on the third + (2) SCSI disk (<filename>da</filename>) respectively. By contrast, a Vinum volume might be called <filename>/dev/vinum/concat</filename>, a name which has no relationship with a partition name.</para> @@ -927,7 +922,7 @@ newfs: /dev/vinum/concat: can't figure out file system partition</screen> </sect2> </sect1> - <sect1 id="vinum-config"> + <sect1 xml:id="vinum-config"> <title>Configuring Vinum</title> <para>The <filename>GENERIC</filename> kernel does not contain @@ -980,7 +975,7 @@ sd name bigraid.p0.s4 drive e plex bigraid.p0 state initializing len 4194304b dr if they have been assigned different &unix; drive IDs.</para> - <sect3 id="vinum-rc-startup"> + <sect3 xml:id="vinum-rc-startup"> <title>Automatic Startup</title> <para>In order to start Vinum automatically when you boot the @@ -1011,7 +1006,7 @@ sd name bigraid.p0.s4 drive e plex bigraid.p0 state initializing len 4194304b dr </sect2> </sect1> - <sect1 id="vinum-root"> + <sect1 xml:id="vinum-root"> <title>Using Vinum for the Root Filesystem</title> <para>For a machine that has fully-mirrored filesystems using @@ -1060,8 +1055,7 @@ sd name bigraid.p0.s4 drive e plex bigraid.p0 state initializing len 4194304b dr Vinum statically into the kernel, so it is available all the time, but this is usually not desirable. There is another option as well, to have - <filename>/boot/loader</filename> (<xref - linkend="boot-loader"/>) load the vinum kernel module + <filename>/boot/loader</filename> (<xref linkend="boot-loader"/>) load the vinum kernel module early, before starting the kernel. This can be accomplished by putting the line:</para> @@ -1081,8 +1075,7 @@ sd name bigraid.p0.s4 drive e plex bigraid.p0 state initializing len 4194304b dr <note><para>The following paragraphs are outlining the steps needed for FreeBSD 5.X and above. The setup required for - FreeBSD 4.X differs, and is described below in <xref - linkend="vinum-root-4x"/>.</para></note> + FreeBSD 4.X differs, and is described below in <xref linkend="vinum-root-4x"/>.</para></note> <para>By placing the line:</para> @@ -1168,13 +1161,13 @@ sd name bigraid.p0.s4 drive e plex bigraid.p0 state initializing len 4194304b dr <step> <para>Run the command:</para> - <screen>&prompt.root; <userinput>disklabel -e <replaceable>devname</replaceable></userinput></screen> + <screen>&prompt.root; <userinput>disklabel -e devname</userinput></screen> <para>for each device that participates in the root volume. <replaceable>devname</replaceable> must be either the name - of the disk (like <devicename>da0</devicename>) for disks + of the disk (like <filename>da0</filename>) for disks without a slice (aka. fdisk) table, or the name of the - slice (like <devicename>ad0s1</devicename>).</para> + slice (like <filename>ad0s1</filename>).</para> <para>If there is already an <literal>"a"</literal> partition on the device (presumably, containing a @@ -1217,7 +1210,7 @@ sd name bigraid.p0.s4 drive e plex bigraid.p0 state initializing len 4194304b dr root volume. It is highly recommendable to verify the result again, using a command like:</para> - <screen>&prompt.root; <userinput>fsck -n /dev/<replaceable>devname</replaceable>a</userinput></screen> + <screen>&prompt.root; <userinput>fsck -n /dev/devnamea</userinput></screen> </step> </procedure> @@ -1364,7 +1357,7 @@ Subdisk root.p1.s0: above.</para> </sect3> - <sect3 id="vinum-root-panic"> + <sect3 xml:id="vinum-root-panic"> <title>Nothing Boots, the Bootstrap Panics</title> @@ -1381,8 +1374,7 @@ Subdisk root.p1.s0: <para>Similarly, if the above situation has been recovered, for example by booting from a <quote>Fixit</quote> medium, and the bootstrap has been re-installed using - <command>disklabel -B</command> as described in <xref - linkend="boot-boot1"/>, the bootstrap will trash the Vinum + <command>disklabel -B</command> as described in <xref linkend="boot-boot1"/>, the bootstrap will trash the Vinum header, and Vinum will no longer find its disk(s). Though no actual Vinum configuration data or data in Vinum volumes will be trashed by this, and it would be possible to recover @@ -1394,7 +1386,7 @@ Subdisk root.p1.s0: </sect3> </sect2> - <sect2 id="vinum-root-4x"> + <sect2 xml:id="vinum-root-4x"> <title>Differences for FreeBSD 4.X</title> <para>Under FreeBSD 4.X, some internal functions required to |