doc-el commit 1080:ca97a1a16a24 - Translate sections 19.2 - 19.3...
freebsd-doc-el at lists.hellug.gr
freebsd-doc-el at lists.hellug.gr
Sat Nov 29 00:02:54 EET 2008
changeset: 1080:ca97a1a16a24
user: Manolis Kiagias <sonicy at otenet.gr>
date: 2008-11-20 15:30 +0200
details: http://hg.hellug.gr/freebsd/doc-el/?cmd=changeset;node=ca97a1a16a24
description:
Translate sections 19.2 - 19.3 ('geom' chapter)
diffstat:
1 file changed, 96 insertions(+), 86 deletions(-)
el_GR.ISO8859-7/books/handbook/geom/chapter.sgml | 182 +++++++++++-----------
diffs (239 lines):
diff -r ac457b3a155e -r ca97a1a16a24 el_GR.ISO8859-7/books/handbook/geom/chapter.sgml
--- a/el_GR.ISO8859-7/books/handbook/geom/chapter.sgml Wed Nov 19 23:20:07 2008 +0200
+++ b/el_GR.ISO8859-7/books/handbook/geom/chapter.sgml Thu Nov 20 15:30:06 2008 +0200
@@ -91,31 +91,32 @@
</sect1>
<sect1 id="GEOM-intro">
- <title>GEOM Introduction</title>
+ <title>ÅéóáãùãÞ óôï GEOM</title>
- <para>GEOM permits access and control to classes — Master Boot
- Records, <acronym>BSD</acronym> labels, etc — through the
- use of providers, or the special files in
- <filename class="directory">/dev</filename>. Supporting various
- software <acronym>RAID</acronym> configurations, GEOM will
- transparently provide access to the operating system and
- operating system utilities.</para>
+ <para>Ôï GEOM åðéôñÝðåé ôçí ðñüóâáóç êáé ôïí Ýëåã÷ï óå êëÜóåéò —
+ üðùò ôçí ÊåíôñéêÞ ÅããñáöÞ Åêêßíçóçò (Master Boot Record), ôá
+ <acronym>BSD</acronym> label, ê.á. — ìÝóù ôçò ÷ñÞóçò ðáñï÷Ýùí,
+ Þ ìÝóù åéäéêþí áñ÷åßùí óôïí êáôÜëïãï
+ <filename class="directory">/dev</filename>. Ôï GEOM õðïóôçñßæåé
+ äéÜöïñåò äéáôÜîåéò <acronym>RAID</acronym> êáé ðáñÝ÷åé äéÜöáíç
+ ðñüóâáóç óôï ëåéôïõñãéêü óýóôçìá êáé ôá âïçèçôéêÜ ôïõ
+ ðñïãñÜììáôá.</para>
</sect1>
<sect1 id="GEOM-striping">
- <sect1info>
- <authorgroup>
- <author>
- <firstname>Tom</firstname>
- <surname>Rhodes</surname>
- <contrib>Written by </contrib>
- </author>
- <author>
- <firstname>Murray</firstname>
- <surname>Stokely</surname>
- </author>
- </authorgroup>
- </sect1info>
+ <sect1info>
+ <authorgroup>
+ <author>
+ <firstname>Tom</firstname>
+ <surname>Rhodes</surname>
+ <contrib>ÃñÜöçêå áðü ôïõò </contrib>
+ </author>
+ <author>
+ <firstname>Murray</firstname>
+ <surname>Stokely</surname>
+ </author>
+ </authorgroup>
+ </sect1info>
<title>RAID0 - Striping</title>
@@ -126,107 +127,116 @@
<primary>Striping</primary>
</indexterm>
- <para>Striping is a method used to combine several disk drives into
- a single volume. In many cases, this is done through the use of
- hardware controllers. The GEOM disk subsystem provides
- software support for <acronym>RAID</acronym>0, also known as
- disk striping.</para>
+ <para>Ôï striping åßíáé ìéá ìÝèïäïò ðïõ óõíäõÜæåé äéáöïñåôéêïýò öõóéêïýò
+ äßóêïõò óå Ýíá ìïíáäéêü ëïãéêü ôüìï. Óå ðïëëÝò ðåñéðôþóåéò, áõôü
+ ãßíåôáé ìå ôçí âïÞèåéá åîåéäéêåõìÝíïõ õëéêïý (åëåãêôþí). Ôï õðïóýóôçìá
+ äßóêùí GEOM ðáñÝ÷åé õðïóôÞñéîç ìÝóù ëïãéóìéêïý ãéá
+ <acronym>RAID</acronym>0, ôï ïðïßï åßíáé ãíùóôü êáé ùò striping.</para>
- <para>In a <acronym>RAID</acronym>0 system, data are split up in
- blocks that get written across all the drives in the array.
- Instead of having to wait on the system to write 256k to one
- disk, a <acronym>RAID</acronym>0 system can simultaneously write
- 64k to each of four different disks, offering superior I/O
- performance. This performance can be enhanced further by using
- multiple disk controllers.</para>
+ <para>Óå Ýíá óýóôçìá <acronym>RAID</acronym>0, ôá äåäïìÝíá ÷ùñßæïíôáé óå
+ blocks ôá ïðïßá ãñÜöïíôáé ôìçìáôéêÜ óå üëïõò ôïõò äßóêïõò ðïõ áðïôåëïýí
+ ôç óõóôïé÷ßá. Áíôß íá ÷ñåéÜæåôáé íá ðåñéìÝíåôå ôï óýóôçìá íá ãñÜøåé
+ 256k äåäïìÝíùí óå Ýíá äßóêï, Ýíá óýóôçìá <acronym>RAID</acronym>0 ìðïñåß
+ íá ãñÜøåé ôáõôü÷ñïíá 64k óå êáèÝíá áðü ôïõò ôÝóóåñéò äßóêïõò ìéáò
+ óõóôïé÷ßáò, ðñïóöÝñïíôáò Ýôóé åîáéñåôéêÞ áðüäïóç åéóüäïõ/åîüäïõ (I/O).
+ Ç áðüäïóç áõôÞ ìðïñåß íá áõîçèåß ðåñéóóüôåñï, ìå ôç ÷ñÞóç ðïëëáðëþí
+ åëåãêôþí äßóêùí.</para>
- <para>Each disk in a <acronym>RAID</acronym>0 stripe must be of
- the same size, since I/O requests are interleaved to read or
- write to multiple disks in parallel.</para>
+ <para>ÊÜèå äßóêïò óå Ýíá stripe <acronym>RAID</acronym>0 ðñÝðåé íá åßíáé
+ ôïõ ßäéïõ ìåãÝèïõò, êáèþò ïé áéôÞóåéò I/O ìïéñÜæïíôáé üóï áöïñÜ ôçí
+ áíÜãíùóç êáé åããñáöÞ, óå ðïëëïýò ðáñÜëëçëïõò äßóêïõò.</para>
- <mediaobject>
- <imageobject>
- <imagedata fileref="geom/striping" align="center">
- </imageobject>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="geom/striping" align="center">
+ </imageobject>
- <textobject>
- <phrase>Disk Striping Illustration</phrase>
- </textobject>
- </mediaobject>
+ <textobject>
+ <phrase>ÄéÜãñáììá Disk Striping</phrase>
+ </textobject>
+ </mediaobject>
<procedure>
- <title>Creating a stripe of unformatted ATA disks</title>
+ <title>Äçìéïõñãßá Stripe áðü ìç-ÄéáìïñöùìÝíïõò ATA Äßóêïõò</title>
- <step><para>Load the <filename>geom_stripe</filename>
- module:</para>
+ <step>
+ <para>Öïñôþóôå ôï Üñèñùìá <filename>geom_stripe</filename>:</para>
- <screen>&prompt.root; <userinput>kldload geom_stripe</userinput></screen>
- </step>
+ <screen>&prompt.root; <userinput>kldload geom_stripe</userinput></screen>
+ </step>
- <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
- class="directory">/mnt</filename>:</para>
+ <step>
+ <para>Åîáóöáëßóôå üôé õðÜñ÷åé êáôÜëëçëï óçìåßï ðñïóÜñôçóçò. Áí ï
+ ôüìïò ðñüêåéôáé íá ãßíåé êáôÜôìçóç root, ðñïóáñôÞóôå ôïí
+ ðñïóùñéíÜ óå êÜðïéï Üëëï óçìåßï ðñïóÜñôçóçò, üðùò ôï
+ <filename class="directory">/mnt</filename>:</para>
<screen>&prompt.root; <userinput>mkdir /mnt</userinput></screen>
</step>
- <step><para>Determine the device names for the disks which will
- be striped, and create the new stripe device. For example,
- to stripe two unused and unpartitioned <acronym>ATA</acronym> disks,
- for example <filename>/dev/ad2</filename> and
- <filename>/dev/ad3</filename>:</para>
+ <step>
+ <para>Êáèïñßóôå ôá ïíüìáôá ôùí óõóêåõþí ãéá ôïõò äßóêïõò ðïõ ðñüêåéôáé
+ íá ãßíïõí stripe, êáé äçìéïõñãÞóôå ôç íÝá óõóêåõÞ stripe. Ãéá
+ ðáñÜäåéãìá, ãéá íá äçìéïõñãÞóåôå Ýíá stripe áðü äýï
+ á÷ñçóéìïðïßçôïõò êáé ÷ùñßò êáôáôìÞóåéò äßóêïõò
+ <acronym>ATA</acronym>, üðùò ð.÷. ôïõò
+ <filename>/dev/ad2</filename> êáé
+ <filename>/dev/ad3</filename>:</para>
<screen>&prompt.root; <userinput>gstripe label -v st0 /dev/ad2 /dev/ad3</userinput></screen>
-<!--
+<!--
<para>A message should be returned explaining that meta data has
been stored on the devices.
XXX: What message? Put it inside the screen output above.
-->
</step>
- <step><para>Write a standard label, also known as a partition
- table, on the new volume and install the default
- bootstrap code:</para>
+ <step>
+ <para>ÃñÜøôå Ýíá ôõðïðïéçìÝíï label (ðßíáêá êáôáôìÞóåùí) óôï íÝï
+ ôüìï, êáé åãêáôáóôÞóôå ôïí ðñïåðéëåãìÝíï êþäéêá åêêßíçóçò
+ (bootstrap):</para>
<screen>&prompt.root; <userinput>bsdlabel -wB /dev/stripe/st0</userinput></screen>
</step>
- <step><para>This process should have created two other devices
- in the <filename class="directory">/dev/stripe</filename>
- directory in addition to the <devicename>st0</devicename> device.
- Those include <devicename>st0a</devicename> and
- <devicename>st0c</devicename>. At this point a file system may be created
- on the <devicename>st0a</devicename> device with the
- <command>newfs</command> utility:</para>
+ <step>
+ <para>Ç äéáäéêáóßá áõôÞ èá äçìéïõñãÞóåé äýï íÝåò óõóêåõÝò óôïí
+ êáôÜëïãï <filename class="directory">/dev/stripe</filename>,
+ åðéðñüóèåôá áðü ôç óõóêåõÞ <devicename>st0</devicename>.
+ Ïé óõóêåõÝò áõôÝò èá ïíïìÜæïíôáé <devicename>st0a</devicename> êáé
+ <devicename>st0c</devicename>. Óôï óçìåßï áõôü, ìðïñåßôå ðëÝïí íá
+ äçìéïõñãÞóåôå óýóôçìá áñ÷åßùí óôç óõóêåõÞ
+ <devicename>st0a</devicename> ÷ñçóéìïðïéþíôáò ôï âïçèçôéêü ðñüãñáììá
+ <command>newfs</command>:</para>
- <screen>&prompt.root; <userinput>newfs -U /dev/stripe/st0a</userinput></screen>
+ <screen>&prompt.root; <userinput>newfs -U /dev/stripe/st0a</userinput></screen>
- <para>Many numbers will glide across the screen, and after a few
- seconds, the process will be complete. The volume has been
- created and is ready to be mounted.</para>
- </step>
- </procedure>
+ <para>Èá äåßôå ìéá ìåãÜëç óåéñÜ áñéèìþí íá ðåñíÜ ãñÞãïñá áðü ôçí
+ ïèüíç óáò, êáé ìåôÜ áðü ëßãá äåõôåñüëåðôá ç äéáäéêáóßá èá Ý÷åé
+ ïëïêëçñùèåß. Ï ôüìïò èá Ý÷åé äçìéïõñãçèåß êáé èá åßíáé Ýôïéìïò
+ ãéá ðñïóÜñôçóç.</para>
+ </step>
+ </procedure>
- <para>To manually mount the created disk stripe:</para>
+ <para>Ãéá íá ðñïóáñôÞóåôå ÷åéñïêßíçôá ôï stripe ðïõ äçìéïõñãÞóáôå:</para>
- <screen>&prompt.root; <userinput>mount /dev/stripe/st0a /mnt</userinput></screen>
+ <screen>&prompt.root; <userinput>mount /dev/stripe/st0a /mnt</userinput></screen>
- <para>To mount this striped file system automatically during the boot
- process, place the volume information in
- <filename>/etc/fstab</filename> file:</para>
+ <para>Ãéá íá ãßíåôáé áõôüìáôá ç ðñïóÜñôçóç áõôïý ôïõ óõóôÞìáôïò áñ÷åßùí
+ êáôÜ ôçí äéáäéêáóßá åêêßíçóçò, ôïðïèåôÞóôå ôéò ðëçñïöïñßåò ôïõ ôüìïõ óôï
+ áñ÷åßï <filename>/etc/fstab</filename>:</para>
- <screen>&prompt.root; <userinput>echo "/dev/stripe/st0a /mnt ufs rw 2 2" \</userinput>
+ <screen>&prompt.root; <userinput>echo "/dev/stripe/st0a /mnt ufs rw 2 2" \</userinput>
<userinput>>> /etc/fstab</userinput></screen>
- <para>The <filename>geom_stripe</filename> module must also be automatically loaded during
- system initialization, by adding a line to
- <filename>/boot/loader.conf</filename>:</para>
+ <para>Èá ðñÝðåé åðßóçò íá öïñôþíåôáé áõôüìáôá ôï Üñèñùìá
+ <filename>geom_stripe</filename> êáôÜ ôçí åêêßíçóç ôïõ óõóôÞìáôïò.
+ ÐñïóèÝóôå ôçí ðáñáêÜôù ãñáììÞ óôï áñ÷åßï
+ <filename>/boot/loader.conf</filename>:</para>
- <screen>&prompt.root; <userinput>echo 'geom_stripe_load="YES"' >> /boot/loader.conf</userinput></screen>
-
+ <screen>&prompt.root; <userinput>echo 'geom_stripe_load="YES"' >> /boot/loader.conf</userinput></screen>
</sect1>
<sect1 id="GEOM-mirror">
More information about the Freebsd-doc-el
mailing list