From owner-svn-doc-head@FreeBSD.ORG Fri Apr 25 18:20:43 2014 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C9F2AEEB; Fri, 25 Apr 2014 18:20:43 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B55091607; Fri, 25 Apr 2014 18:20:43 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s3PIKh8j067509; Fri, 25 Apr 2014 18:20:43 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s3PIKhdR067508; Fri, 25 Apr 2014 18:20:43 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201404251820.s3PIKhdR067508@svn.freebsd.org> From: Dru Lavigne Date: Fri, 25 Apr 2014 18:20:43 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r44666 - head/en_US.ISO8859-1/books/handbook/geom X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Apr 2014 18:20:43 -0000 Author: dru Date: Fri Apr 25 18:20:43 2014 New Revision: 44666 URL: http://svnweb.freebsd.org/changeset/doc/44666 Log: White space fix only. Translators can ignore. Sponsored by: iXsystems Modified: head/en_US.ISO8859-1/books/handbook/geom/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/geom/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/geom/chapter.xml Fri Apr 25 17:52:12 2014 (r44665) +++ head/en_US.ISO8859-1/books/handbook/geom/chapter.xml Fri Apr 25 18:20:43 2014 (r44666) @@ -273,12 +273,12 @@ Done. replace the failed drive without user interruption. Two common situations are illustrated in these examples. - The first creates a mirror out of two new drives and uses it - as a replacement for an existing single drive. The second - example creates a mirror on a single new drive, copies the old - drive's data to it, then inserts the old drive into the - mirror. While this procedure is slightly more complicated, it - only requires one new drive. + The first creates a mirror out of two new drives and uses it as + a replacement for an existing single drive. The second example + creates a mirror on a single new drive, copies the old drive's + data to it, then inserts the old drive into the mirror. While + this procedure is slightly more complicated, it only requires + one new drive. Traditionally, the two drives in a mirror are identical in model and capacity, but &man.gmirror.8; does not require that. @@ -295,8 +295,8 @@ Done. - While dump is used in these procedures to copy file - systems, it does not work on file systems with + While dump is used in these procedures + to copy file systems, it does not work on file systems with soft updates journaling. See &man.tunefs.8; for information on detecting and disabling soft updates journaling. @@ -307,19 +307,20 @@ Done. Many disk systems store metadata at the end of each disk. Old metadata should be erased before reusing the disk for a mirror. Most problems are caused by two particular types of - leftover metadata: GPT partition tables and old - metadata from a previous mirror. + leftover metadata: GPT partition tables and + old metadata from a previous mirror. - GPT metadata can be erased with gpart. This - example erases both primary and backup GPT partition tables - from disk ada8: + GPT metadata can be erased with + gpart. This example erases both primary + and backup GPT partition tables from disk + ada8: &prompt.root; gpart destroy -F ada8 A disk can be removed from an active mirror and the - metadata erased in one step using gmirror. Here, the example disk - ada8 is removed from the active - mirror gm4: + metadata erased in one step using gmirror. + Here, the example disk ada8 is removed + from the active mirror gm4: &prompt.root; gmirror remove gm4 ada8 @@ -329,12 +330,15 @@ Done. &prompt.root; gmirror clear ada8 - When gmirror is used, one block of metadata is stored at the end of - the disk. Because GPT partition schemes also store metadata - at the end of the disk, mirroring entire GPT disks with - gmirror is not recommended. MBR partitioning is used - here because it only stores a partition table at the start of - the disk and does not conflict with gmirror. + When gmirror is used, one block of + metadata is stored at the end of the disk. Because + GPT partition schemes also store metadata + at the end of the disk, mirroring entire + GPT disks with gmirror + is not recommended. MBR partitioning is + used here because it only stores a partition table at the + start of the disk and does not conflict with + gmirror. @@ -342,15 +346,14 @@ Done. In this example, &os; has already been installed on a single disk, ada0. Two new disks, - ada1 and - ada2, have been connected to the - system. A new mirror will be created on these two disks and - used to replace the old single disk. - - The - geom_mirror.ko kernel module must either be built into the - kernel or loaded at boot- or run-time. Manually load the - kernel module now: + ada1 and ada2, have + been connected to the system. A new mirror will be created on + these two disks and used to replace the old single + disk. + + The geom_mirror.ko kernel module must + either be built into the kernel or loaded at boot- or + run-time. Manually load the kernel module now: &prompt.root; gmirror load @@ -358,15 +361,16 @@ Done. &prompt.root; gmirror label -v gm0 /dev/ada1 /dev/ada2 - In this example, gm0 is a user-chosen device name - assigned to the new mirror. After the mirror has been - started, this device name will appear in + In this example, gm0 is a user-chosen + device name assigned to the new mirror. After the mirror has + been started, this device name will appear in /dev/mirror/. - MBR and bsdlabel partition tables can now be created on - the mirror with gpart. This example uses a traditional - file system layout, with partitions for - /, swap, /var, + MBR and + bsdlabel partition tables can now + be created on the mirror with gpart. This + example uses a traditional file system layout, with partitions + for /, swap, /var, /tmp, and /usr. A single / file system and a swap partition will also work. @@ -400,8 +404,9 @@ Done. 18874370 137426928 6 freebsd-ufs (65G) 156301298 1 - free - (512B) - Make the mirror bootable by installing bootcode in the MBR - and bsdlabel and setting the active slice: + Make the mirror bootable by installing bootcode in the + MBR and bsdlabel and setting the active + slice: &prompt.root; gpart bootcode -b /boot/mbr mirror/gm0 &prompt.root; gpart set -a active -i 1 mirror/gm0 @@ -415,9 +420,9 @@ Done. &prompt.root; newfs -U /dev/mirror/gm0s1e &prompt.root; newfs -U /dev/mirror/gm0s1f - File systems from the original - ada0 disk can now be copied onto the - mirror with dump and restore. + File systems from the original ada0 + disk can now be copied onto the mirror with + dump and restore. &prompt.root; mount /dev/mirror/gm0s1a /mnt &prompt.root; dump -C16 -b64 -0aL -f - / | (cd /mnt && restore -rf -) @@ -428,8 +433,8 @@ Done. &prompt.root; dump -C16 -b64 -0aL -f - /tmp | (cd /mnt/tmp && restore -rf -) &prompt.root; dump -C16 -b64 -0aL -f - /usr | (cd /mnt/usr && restore -rf -) - Next, edit /mnt/etc/fstab to - point to the new mirror file systems: + Next, edit /mnt/etc/fstab to point to + the new mirror file systems: # Device Mountpoint FStype Options Dump Pass# /dev/mirror/gm0s1a / ufs rw 1 1 @@ -438,23 +443,23 @@ Done. /dev/mirror/gm0s1e /tmp ufs rw 2 2 /dev/mirror/gm0s1f /usr ufs rw 2 2 - If the geom_mirror.ko kernel module has not been built - into the kernel, /mnt/boot/loader.conf is - edited to load the module at boot: + If the geom_mirror.ko kernel module + has not been built into the kernel, + /mnt/boot/loader.conf is edited to load + the module at boot: geom_mirror_load="YES" Reboot the system to test the new mirror and verify that - all data has been copied. The BIOS will see the mirror as two - individual drives rather than a mirror. Because the drives - are identical, it does not matter which is selected to - boot. - - See - if there are problems booting. Powering down and - disconnecting the original ada0 disk - will allow it to be kept as an offline backup. + all data has been copied. The BIOS will + see the mirror as two individual drives rather than a mirror. + Because the drives are identical, it does not matter which is + selected to boot. + + See if there are + problems booting. Powering down and disconnecting the + original ada0 disk will allow it to be + kept as an offline backup. In use, the mirror will behave just like the original single drive. @@ -465,16 +470,17 @@ Done. In this example, &os; has already been installed on a single disk, ada0. A new disk, - ada1, has been connected to the - system. A one-disk mirror will be created on the new disk, - the existing system copied onto it, and then the old disk will - be inserted into the mirror. This slightly complex procedure - is required because gmirror needs to put a 512-byte - block of metadata at the end of each disk, and the existing - ada0 has usually had all of its space - already allocated. + ada1, has been connected to the system. + A one-disk mirror will be created on the new disk, the + existing system copied onto it, and then the old disk will be + inserted into the mirror. This slightly complex procedure is + required because gmirror needs to put a + 512-byte block of metadata at the end of each disk, and the + existing ada0 has usually had all of its + space already allocated. - Load the geom_mirror.ko kernel module: + Load the geom_mirror.ko kernel + module: &prompt.root; gmirror load @@ -488,15 +494,16 @@ Done. Create a mirror on the new disk. To make certain that the mirror capacity is not any larger than the original drive, - gnop is used to create a fake drive of the exact same - size. This drive does not store any data, but is used only to - limit the size of the mirror. When gmirror creates - the mirror, it will restrict the capacity to the size of + gnop is used to create a fake drive of the + exact same size. This drive does not store any data, but is + used only to limit the size of the mirror. When + gmirror creates the mirror, it will + restrict the capacity to the size of gzero.nop, even if the new drive (ada1) has more space. Note that the 1000204821504 in the second line - should be equal to ada0's media size - as shown by diskinfo above. + should be equal to ada0's media size as + shown by diskinfo above. &prompt.root; geom zero load &prompt.root; gnop create -s 1000204821504 gzero @@ -504,22 +511,22 @@ Done. &prompt.root; gmirror forget gm0 Since gzero.nop does not store any - data, the mirror does not see it as connected. The mirror - is told to forget unconnected components, - removing references to gzero.nop. - The result is a mirror device containing only a single disk, + data, the mirror does not see it as connected. The mirror is + told to forget unconnected components, removing + references to gzero.nop. The result is a + mirror device containing only a single disk, ada1. After creating gm0, view the - partition table on ada0. This output is from a 1 TB drive. If there is some - unallocated space at the end of the drive, the contents may be - copied directly from ada0 to the new - mirror. + partition table on ada0. This output is + from a 1 TB drive. If there is some unallocated space at + the end of the drive, the contents may be copied directly from + ada0 to the new mirror. However, if the output shows that all of the space on the disk is allocated, like in the following listing, there is no - space available for the 512-byte mirror metadata at - the end of the disk. + space available for the 512-byte mirror metadata at the end of + the disk. &prompt.root; gpart show ada0 => 63 1953525105 ada0 MBR (931G) @@ -527,8 +534,8 @@ Done. In this case, the partition table must be edited to reduce the capacity by one sector on - mirror/gm0. The procedure will - be explained later. + mirror/gm0. The procedure will be + explained later. In either case, partition tables on the primary disk should be first copied using gpart backup @@ -589,9 +596,8 @@ BSD 8 gm0s1a for /, gm0s1d for /var, gm0s1e for /usr, - gm0s1f for - /data1, and - gm0s1g for + gm0s1f for /data1, + and gm0s1g for /data2. &prompt.root; gpart show mirror/gm0 @@ -612,8 +618,8 @@ BSD 8 Both the slice and the last partition should have some free space at the end of each disk. - Create file systems on these new partitions. The - number of partitions will vary, matching the partitions on the + Create file systems on these new partitions. The number + of partitions will vary, matching the partitions on the original disk, ada0. &prompt.root; newfs -U /dev/mirror/gm0s1a @@ -622,16 +628,17 @@ BSD 8 &prompt.root; newfs -U /dev/mirror/gm0s1f &prompt.root; newfs -U /dev/mirror/gm0s1g - Make the mirror bootable by installing bootcode in the MBR - and bsdlabel and setting the active slice: + Make the mirror bootable by installing bootcode in the + MBR and bsdlabel and setting the active + slice: &prompt.root; gpart bootcode -b /boot/mbr mirror/gm0 &prompt.root; gpart set -a active -i 1 mirror/gm0 &prompt.root; gpart bootcode -b /boot/boot mirror/gm0s1 - Adjust /etc/fstab to use the - new partitions on the mirror. Back up this file first by - copying it to /etc/fstab.orig. + Adjust /etc/fstab to use the new + partitions on the mirror. Back up this file first by copying + it to /etc/fstab.orig. &prompt.root; cp /etc/fstab /etc/fstab.orig @@ -647,16 +654,17 @@ BSD 8 /dev/mirror/gm0s1f /data1 ufs rw 2 2 /dev/mirror/gm0s1g /data2 ufs rw 2 2 - If the geom_mirror.ko kernel module has not been built - into the kernel, edit /boot/loader.conf - to load it: + If the geom_mirror.ko kernel module + has not been built into the kernel, edit + /boot/loader.conf to load it: geom_mirror_load="YES" File systems from the original disk can now be copied onto - the mirror with dump and restore. Note that - it may take some time to create a snapshot for each file system - dumped with dump -L. + the mirror with dump and + restore. Note that it may take some time + to create a snapshot for each file system dumped with + dump -L. &prompt.root; mount /dev/mirror/gm0s1a /mnt &prompt.root; dump -C16 -b64 -0aL -f - / | (cd /mnt && restore -rf -) @@ -671,11 +679,10 @@ BSD 8 Restart the system, booting from ada1. If everything is working, the - system will boot from mirror/gm0, - which now contains the same data as - ada0 had previously. See - - if there are problems booting. + system will boot from mirror/gm0, which + now contains the same data as ada0 had + previously. See if + there are problems booting. At this point, the mirror still consists of only the single ada1 disk. @@ -691,18 +698,19 @@ BSD 8 mirror/gm0 has the same contents as ada0 before adding ada0 to the mirror. If there is - something wrong with the contents copied by dump and - restore, revert /etc/fstab to - mount the file systems on ada0, - reboot, and try the whole procedure again. + something wrong with the contents copied by + dump and restore, + revert /etc/fstab to mount the file + systems on ada0, reboot, and try the + whole procedure again. &prompt.root; gmirror insert gm0 ada0 GEOM_MIRROR: Device gm0: rebuilding provider ada0 Synchronization between the two disks will start - immediately. Use gmirror status - to view the progress. + immediately. Use gmirror status to view + the progress. &prompt.root; gmirror status Name Status Components @@ -717,10 +725,10 @@ mirror/gm0 DEGRADED ada1 (ACTIVE) mirror/gm0 COMPLETE ada1 (ACTIVE) ada0 (ACTIVE) - The mirror, mirror/gm0, now consists of - the two disks ada0 and - ada1, and the contents are - automatically synchronized with each other. In use, + The mirror, mirror/gm0, now consists + of the two disks ada0 and + ada1, and the contents are automatically + synchronized with each other. In use, mirror/gm0 will behave just like the original single drive. @@ -729,14 +737,14 @@ mirror/gm0 COMPLETE ada1 (ACTIVE) Troubleshooting If the system no longer boots, BIOS - settings may have to be changed to boot from one - of the new mirrored drives. Either mirror drive can be - used for booting, as they contain identical data. + settings may have to be changed to boot from one of the new + mirrored drives. Either mirror drive can be used for booting, + as they contain identical data. - If the boot stops with this message, something is - wrong with the mirror device: + If the boot stops with this message, something is wrong + with the mirror device: - Mounting from ufs:/dev/mirror/gm0s1a failed with error 19. + Mounting from ufs:/dev/mirror/gm0s1a failed with error 19. Loader variables: vfs.root.mountfrom=ufs:/dev/mirror/gm0s1a @@ -758,38 +766,35 @@ Manual root filesystem specification: mountroot> - Forgetting to load the - geom_mirror.ko module in - /boot/loader.conf can cause this - problem. To fix it, boot from a &os; 9.0 or later - installation media and choose Shell at - the first prompt. Then load the mirror module and mount - the mirror device: + Forgetting to load the geom_mirror.ko + module in /boot/loader.conf can cause + this problem. To fix it, boot from a &os; 9.0 or later + installation media and choose Shell at the + first prompt. Then load the mirror module and mount the + mirror device: - &prompt.root; gmirror load + &prompt.root; gmirror load &prompt.root; mount /dev/mirror/gm0s1a /mnt - Edit /mnt/boot/loader.conf, - adding a line to load the mirror module: + Edit /mnt/boot/loader.conf, adding a + line to load the mirror module: - geom_mirror_load="YES" + geom_mirror_load="YES" - Save the file and reboot. + Save the file and reboot. - Other problems that cause error 19 - require more effort to fix. Although the system should boot from - ada0, another prompt to select a - shell will appear if /etc/fstab is - incorrect. Enter - ufs:/dev/ada0s1a at the boot loader - prompt and press Enter. Undo the - edits in - /etc/fstab then mount the file systems from - the original disk (ada0) instead - of the mirror. Reboot the system and try the procedure - again. + Other problems that cause error 19 + require more effort to fix. Although the system should boot + from ada0, another prompt to select a + shell will appear if /etc/fstab is + incorrect. Enter ufs:/dev/ada0s1a at the + boot loader prompt and press Enter. Undo the + edits in /etc/fstab then mount the file + systems from the original disk (ada0) + instead of the mirror. Reboot the system and try the + procedure again. - Enter full pathname of shell or RETURN for /bin/sh: + Enter full pathname of shell or RETURN for /bin/sh: &prompt.root; cp /etc/fstab.orig /etc/fstab &prompt.root; reboot @@ -799,9 +804,9 @@ mountroot> The benefit of disk mirroring is that an individual disk can fail without causing the mirror to lose any data. In the - above example, if ada0 fails, the - mirror will continue to work, providing data from the - remaining working drive, ada1. + above example, if ada0 fails, the mirror + will continue to work, providing data from the remaining + working drive, ada1. To replace the failed drive, shut down the system and physically replace the failed drive with a new drive of equal @@ -819,8 +824,9 @@ mountroot> &prompt.root; gmirror forget gm0 - Any old metadata should be cleared from the replacement disk using the instructions in - . Then the disk, + Any old metadata should be cleared from the replacement + disk using the instructions in . Then the disk, ada4 for this example, is inserted into the mirror: @@ -895,31 +901,31 @@ mountroot> In a RAID3 system, data is split up into a number of bytes that are written across all the drives in the array except for one disk which acts as a dedicated parity disk. - This means that disk reads from a - RAID3 implementation access all disks in - the array. Performance can be enhanced by using multiple disk - controllers. The RAID3 array provides a - fault tolerance of 1 drive, while providing a capacity of 1 - - 1/n times the total capacity of all drives in the array, where n - is the number of hard drives in the array. Such a configuration - is mostly suitable for storing data of larger sizes such as - multimedia files. + This means that disk reads from a RAID3 + implementation access all disks in the array. Performance can + be enhanced by using multiple disk controllers. The + RAID3 array provides a fault tolerance of 1 + drive, while providing a capacity of 1 - 1/n times the total + capacity of all drives in the array, where n is the number of + hard drives in the array. Such a configuration is mostly + suitable for storing data of larger sizes such as multimedia + files. At least 3 physical hard drives are required to build a RAID3 array. Each disk must be of the same - size, since I/O requests are interleaved to read or write to - multiple disks in parallel. Also, due to the nature of - RAID3, the number of drives must be + size, since I/O requests are interleaved to + read or write to multiple disks in parallel. Also, due to the + nature of RAID3, the number of drives must be equal to 3, 5, 9, 17, and so on, or 2^n + 1. - + This section demonstrates how to create a software RAID3 on a &os; system. - - While it is theoretically possible to boot from a - RAID3 array on &os;, that configuration - is uncommon and is not advised. - + + While it is theoretically possible to boot from a + RAID3 array on &os;, that configuration is + uncommon and is not advised. + Creating a Dedicated <acronym>RAID</acronym>3 @@ -927,14 +933,14 @@ mountroot></screen> <para>In &os;, support for <acronym>RAID</acronym>3 is implemented by the &man.graid3.8; <acronym>GEOM</acronym> - class. Creating a dedicated - <acronym>RAID</acronym>3 array on &os; requires the following - steps.</para> + class. Creating a dedicated <acronym>RAID</acronym>3 array on + &os; requires the following steps.</para> <procedure> <step> <para>First, load the <filename>geom_raid3.ko</filename> - kernel module by issuing one of the following commands:</para> + kernel module by issuing one of the following + commands:</para> <screen>&prompt.root; <userinput>graid3 load</userinput></screen> @@ -944,9 +950,9 @@ mountroot></screen> </step> <step> - <para>Ensure that a suitable mount point - exists. This command creates a new directory to use as - the mount point:</para> + <para>Ensure that a suitable mount point exists. This + command creates a new directory to use as the mount + point:</para> <screen>&prompt.root; <userinput>mkdir <replaceable>/multimedia</replaceable></userinput></screen> </step> @@ -955,15 +961,13 @@ mountroot></screen> <para>Determine the device names for the disks which will be added to the array, and create the new <acronym>RAID</acronym>3 device. The final device listed - will act as the dedicated parity disk. This - example uses three unpartitioned - <acronym>ATA</acronym> drives: - <filename><replaceable>ada1</replaceable></filename> - and - <filename><replaceable>ada2</replaceable></filename> - for data, and - <filename><replaceable>ada3</replaceable></filename> - for parity.</para> + will act as the dedicated parity disk. This example uses + three unpartitioned <acronym>ATA</acronym> drives: + <filename><replaceable>ada1</replaceable></filename> and + <filename><replaceable>ada2</replaceable></filename> for + data, and + <filename><replaceable>ada3</replaceable></filename> for + parity.</para> <screen>&prompt.root; <userinput>graid3 label -v gr0 /dev/ada1 /dev/ada2 /dev/ada3</userinput> Metadata value stored on /dev/ada1. @@ -973,9 +977,9 @@ Done.</screen> </step> <step> - <para>Partition the newly created - <filename>gr0</filename> device and put a <acronym>UFS</acronym> file - system on it:</para> + <para>Partition the newly created <filename>gr0</filename> + device and put a <acronym>UFS</acronym> file system on + it:</para> <screen>&prompt.root; <userinput>gpart create -s GPT /dev/raid3/gr0</userinput> &prompt.root; <userinput>gpart add -t freebsd-ufs /dev/raid3/gr0</userinput> @@ -992,8 +996,8 @@ Done.</screen> </step> </procedure> - <para>Additional configuration is needed to retain this - setup across system reboots.</para> + <para>Additional configuration is needed to retain this setup + across system reboots.</para> <procedure> <step> @@ -1009,8 +1013,8 @@ Done.</screen> <step> <para>The following volume information must be added to <filename>/etc/fstab</filename> in order to - automatically mount the array's file system during - the system boot process:</para> + automatically mount the array's file system during the + system boot process:</para> <programlisting>/dev/raid3/gr0p1 /multimedia ufs rw 2 2</programlisting> </step> @@ -1107,16 +1111,16 @@ raid/r0 OPTIMAL ada0 (ACTIVE (ACTIVE)) <para>The array device appears in <filename>/dev/raid/</filename>. The first array is called - <filename>r0</filename>. Additional arrays, if present, - will be <filename>r1</filename>, - <filename>r2</filename>, and so on.</para> + <filename>r0</filename>. Additional arrays, if present, will + be <filename>r1</filename>, <filename>r2</filename>, and so + on.</para> <para>The <acronym>BIOS</acronym> menu on some of these devices can create arrays with special characters in their names. To avoid problems with those special characters, arrays are given - simple numbered names like <filename>r0</filename>. To - show the actual labels, like <filename>gm0</filename> in - the example above, use &man.sysctl.8;:</para> + simple numbered names like <filename>r0</filename>. To show + the actual labels, like <filename>gm0</filename> in the + example above, use &man.sysctl.8;:</para> <screen>&prompt.root; <userinput>sysctl kern.geom.raid.name_format=1</userinput></screen> </sect2> @@ -1334,8 +1338,8 @@ raid/r0 OPTIMAL ada0 (ACTIVE (ACTIVE)) <para><acronym>GEOM</acronym> provides a simple mechanism for providing remote access to devices such as disks, - <acronym>CD</acronym>s, and file systems through the use - of the <acronym>GEOM</acronym> Gate network daemon, + <acronym>CD</acronym>s, and file systems through the use of the + <acronym>GEOM</acronym> Gate network daemon, <application>ggated</application>. The system with the device runs the server daemon which handles requests made by clients using <application>ggatec</application>. The devices should not @@ -1344,50 +1348,50 @@ raid/r0 OPTIMAL ada0 (ACTIVE (ACTIVE)) <para>Similar to <acronym>NFS</acronym>, which is discussed in <xref linkend="network-nfs"/>, <application>ggated</application> - is configured using an exports file. This file - specifies which systems are permitted to access the exported resources and - what level of access they are offered. For example, to give - the client <systemitem - class="ipaddress">192.168.1.5</systemitem> read and write - access to the fourth slice on the first <acronym>SCSI</acronym> - disk, create <filename>/etc/gg.exports</filename> with this - line:</para> + is configured using an exports file. This file specifies which + systems are permitted to access the exported resources and what + level of access they are offered. For example, to give the + client <systemitem class="ipaddress">192.168.1.5</systemitem> + read and write access to the fourth slice on the first + <acronym>SCSI</acronym> disk, create + <filename>/etc/gg.exports</filename> with this line:</para> <programlisting>192.168.1.5 RW /dev/da0s4d</programlisting> - <para>Before exporting the device, ensure it is not currently mounted. - Then, start <application>ggated</application>:</para> + <para>Before exporting the device, ensure it is not currently + mounted. Then, start <application>ggated</application>:</para> <screen>&prompt.root; <userinput>ggated</userinput></screen> - + <para>Several options are available for specifying an alternate listening port or changing the default location of the exports file. Refer to &man.ggated.8; for details.</para> - <para>To access the exported device on the client - machine, first use <command>ggatec</command> to specify the + <para>To access the exported device on the client machine, first + use <command>ggatec</command> to specify the <acronym>IP</acronym> address of the server and the device name - of the exported device. If successful, this command will display - a <literal>ggate</literal> device name to mount. Mount that - specified device name on a free mount point. This example + of the exported device. If successful, this command will + display a <literal>ggate</literal> device name to mount. Mount + that specified device name on a free mount point. This example connects to the <filename>/dev/da0s4d</filename> partition on <literal>192.168.1.1</literal>, then mounts - <filename>/dev/ggate0</filename> on <filename>/mnt</filename>:</para> + <filename>/dev/ggate0</filename> on + <filename>/mnt</filename>:</para> <screen>&prompt.root; <userinput>ggatec create -o rw 192.168.1.1 /dev/da0s4d</userinput> ggate0 &prompt.root; <userinput>mount /dev/ggate0 /mnt</userinput></screen> <para>The device on the server may now be accessed through - <filename>/mnt</filename> on the client. For more - details about <command>ggatec</command> and a few usage - examples, refer to &man.ggatec.8;.</para> + <filename>/mnt</filename> on the client. For more details about + <command>ggatec</command> and a few usage examples, refer to + &man.ggatec.8;.</para> <note> - <para>The mount will fail if the device is currently mounted - on either the server or any other client on the - network. If simultaneous access is needed to network - resources, use <acronym>NFS</acronym> instead.</para> + <para>The mount will fail if the device is currently mounted on + either the server or any other client on the network. If + simultaneous access is needed to network resources, use + <acronym>NFS</acronym> instead.</para> </note> <para>When the device is no longer needed, unmount it with