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

Few nits found while translating 'vinum' to Greek:

Browse source 
- Add a missing word
- Replace FreeBSD with &os; and add few   where needed
- Add 'class' attributes to several <filename> tags
- Relocate a </note> tag to a more suitable position
This commit is contained in:
Manolis Kiagias 2009-06-29 18:51:34 +00:00
parent b73f116195
commit 190a57f450
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=34497
1 changed files with 29 additions and 29 deletions

58
en_US.ISO8859-1/books/handbook/vinum/chapter.sgml
View file

@ -46,7 +46,7 @@
implemented. One way some users safeguard themselves against such
issues is through the use of multiple, and sometimes redundant,
disks. In addition to supporting various cards and controllers
for hardware RAID systems, the base FreeBSD system includes the
for hardware RAID systems, the base &os; system includes the
Vinum Volume Manager, a block device driver that implements
virtual disk drives. <emphasis>Vinum</emphasis> is a
so-called <emphasis>Volume Manager</emphasis>, a virtual disk
@ -60,7 +60,7 @@
Manager.</para>
<note>
<para>Starting with FreeBSD 5, Vinum has been rewritten in order
<para>Starting with &os;&nbsp;5, Vinum has been rewritten in order
to fit into the GEOM architecture (<xref linkend="GEOM">),
retaining the original ideas, terminology, and on-disk
metadata. This rewrite is called <emphasis>gvinum</emphasis>
@ -72,8 +72,8 @@
kernel module has been changed
from <filename>vinum.ko</filename>
to <filename>geom_vinum.ko</filename>, and all device nodes
reside under <filename>/dev/gvinum</filename> instead
of <filename>/dev/vinum</filename>. As of FreeBSD 6, the old
reside under <filename class="directory">/dev/gvinum</filename> instead
of <filename class="directory">/dev/vinum</filename>. As of &os;&nbsp;6, the old
Vinum implementation is no longer available in the code
base.</para>
</note>
@ -272,7 +272,7 @@
5. Of these, <acronym>RAID-5</acronym> is the most
interesting. As implemented in Vinum, it is a variant on a
striped organization which dedicates one block of each stripe
to parity of the other blocks. As implemented by Vinum, a
to parity one of the other blocks. As implemented by Vinum, a
<acronym>RAID-5</acronym> plex is similar to a striped plex,
except that it implements <acronym>RAID-5</acronym> by
including a parity block in each stripe. As required by
@ -394,7 +394,7 @@
<sect2>
<title>Which Plex Organization?</title>
<para>The version of Vinum supplied with FreeBSD &rel.current; implements
<para>The version of Vinum supplied with &os;&nbsp;&rel.current; implements
two kinds of plex:</para>
<itemizedlist>
@ -761,7 +761,7 @@
drives may be up to 32 characters long.</para>
<para>Vinum objects are assigned device nodes in the hierarchy
<filename>/dev/gvinum</filename>. The configuration shown above
<filename class="directory">/dev/gvinum</filename>. The configuration shown above
would cause Vinum to create the following device nodes:</para>
<itemizedlist>
@ -770,8 +770,8 @@
implemenation.</para></note>
<para>The control devices
<filename>/dev/vinum/control</filename> and
<filename>/dev/vinum/controld</filename>, which are used
<filename class="devicefile">/dev/vinum/control</filename> and
<filename class="devicefile">/dev/vinum/controld</filename>, which are used
by &man.gvinum.8; and the Vinum daemon respectively.</para>
</listitem>
@ -779,31 +779,31 @@
<para>Device entries for each volume.
These are the main devices used by Vinum. Thus the configuration
above would include the devices
<filename>/dev/gvinum/myvol</filename>,
<filename>/dev/gvinum/mirror</filename>,
<filename>/dev/gvinum/striped</filename>,
<filename>/dev/gvinum/raid5</filename> and
<filename>/dev/gvinum/raid10</filename>.</para>
<filename class="devicefile">/dev/gvinum/myvol</filename>,
<filename class="devicefile">/dev/gvinum/mirror</filename>,
<filename class="devicefile">/dev/gvinum/striped</filename>,
<filename class="devicefile">/dev/gvinum/raid5</filename> and
<filename class="devicefile">/dev/gvinum/raid10</filename>.</para>
</listitem>
<listitem>
<note><para>This only applies to the historic Vinum
implemenation.</para></note>
<para>A directory <filename>/dev/vinum/drive</filename>
<para>A directory <filename class="directory">/dev/vinum/drive</filename>
with entries for each drive. These entries are in fact
symbolic links to the corresponding disk nodes.</para>
</listitem>
<listitem>
<para>All volumes get direct entries under
<filename>/dev/gvinum/</filename>.</para>
<filename class="directory">/dev/gvinum/</filename>.</para>
</listitem>
<listitem>
<para>The directories
<filename>/dev/gvinum/plex</filename>, and
<filename>/dev/gvinum/sd</filename>, which contain
<filename class="directory">/dev/gvinum/plex</filename>, and
<filename class="directory">/dev/gvinum/sd</filename>, which contain
device nodes for each plex and for each subdisk,
respectively.</para>
</listitem>
@ -823,7 +823,7 @@
sd length 100m drive drive4</programlisting>
<para>After processing this file, &man.gvinum.8; creates the following
structure in <filename>/dev/gvinum</filename>:</para>
structure in <filename class="directory">/dev/gvinum</filename>:</para>
<programlisting>
drwxr-xr-x 2 root wheel 512 Apr 13 16:46 plex
@ -857,14 +857,14 @@
utilities, notably &man.newfs.8;, which previously tried to
interpret the last letter of a Vinum volume name as a
partition identifier. For example, a disk drive may have a
name like <filename>/dev/ad0a</filename> or
<filename>/dev/da2h</filename>. These names represent
name like <filename class="devicefile">/dev/ad0a</filename> or
<filename class="devicefile">/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.
By contrast, a Vinum volume might be called
<filename>/dev/gvinum/concat</filename>, a name which has
<filename class="devicefile">/dev/gvinum/concat</filename>, a name which has
no relationship with a partition name.</para>
<para>Normally, &man.newfs.8; interprets the name of the disk and
@ -879,10 +879,10 @@ newfs: /dev/gvinum/concat: can't figure out file system partition</screen>
<screen>&prompt.root; <userinput>newfs /dev/gvinum/concat</userinput></screen>
<note><para>On &os; versions prior to 5.0 &man.newfs.8; requires
an additional -v flag and the old device naming
scheme:</para></note>
an additional <option>-v</option> flag and the old device naming
scheme:</para>
<screen>&prompt.root; <userinput>newfs -v /dev/vinum/concat</userinput></screen>
<screen>&prompt.root; <userinput>newfs -v /dev/vinum/concat</userinput></screen></note>
</sect2>
</sect1>
@ -1055,7 +1055,7 @@ sd name bigraid.p0.s4 drive e plex bigraid.p0 state initializing len 4194304b dr
start</command> command.</para>
<note><para>The following paragraphs are outlining the steps
needed for FreeBSD.</para></note>
needed for &os;.</para></note>
<para>By placing the line:</para>
@ -1081,7 +1081,7 @@ sd name bigraid.p0.s4 drive e plex bigraid.p0 state initializing len 4194304b dr
<title>Making a Vinum-based Root Volume Accessible to the
Bootstrap</title>
<para>Since the current FreeBSD bootstrap is only 7.5 KB of
<para>Since the current &os; bootstrap is only 7.5 KB of
code, and already has the burden of reading files (like
<filename>/boot/loader</filename>) from the UFS filesystem, it
is sheer impossible to also teach it about internal Vinum
@ -1235,10 +1235,10 @@ Subdisk root.p1.s0:
<para>The values to note are <literal>135680</literal> for the
offset (relative to partition
<filename>/dev/da0h</filename>). This translates to 265
<filename class="devicefile">/dev/da0h</filename>). This translates to 265
512-byte disk blocks in <command>bsdlabel</command>'s terms.
Likewise, the size of this root volume is 245760 512-byte
blocks. <filename>/dev/da1h</filename>, containing the
blocks. <filename class="devicefile">/dev/da1h</filename>, containing the
second replica of this root volume, has a symmetric
setup.</para>