From owner-svn-doc-all@FreeBSD.ORG Fri Apr 11 17:06:12 2014 Return-Path: Delivered-To: svn-doc-all@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 DA3548F5; Fri, 11 Apr 2014 17:06:12 +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 C5AE914CA; Fri, 11 Apr 2014 17:06:12 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s3BH6CkO046159; Fri, 11 Apr 2014 17:06:12 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s3BH6CJN046158; Fri, 11 Apr 2014 17:06:12 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201404111706.s3BH6CJN046158@svn.freebsd.org> From: Dru Lavigne Date: Fri, 11 Apr 2014 17:06:12 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r44536 - 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-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Apr 2014 17:06:12 -0000 Author: dru Date: Fri Apr 11 17:06:12 2014 New Revision: 44536 URL: http://svnweb.freebsd.org/changeset/doc/44536 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 11 16:46:10 2014 (r44535) +++ head/en_US.ISO8859-1/books/handbook/geom/chapter.xml Fri Apr 11 17:06:12 2014 (r44536) @@ -33,20 +33,21 @@ GEOM - In &os;, the GEOM framework permits access and control to classes, such as Master - Boot Records and BSD labels, through the use - of providers, or the disk devices in /dev. - By supporting various software RAID - configurations, GEOM transparently provides access to the + In &os;, the GEOM framework permits + access and control to classes, such as Master Boot Records and + BSD labels, through the use of providers, or + the disk devices in /dev. By supporting + various software RAID configurations, + GEOM transparently provides access to the operating system and operating system utilities. - This chapter covers the use of disks under the GEOM - framework in &os;. This includes the major RAID - control utilities which use the framework for configuration. - This chapter is - not a definitive guide to RAID configurations - and only GEOM-supported RAID classifications - are discussed. + This chapter covers the use of disks under the + GEOM framework in &os;. This includes the + major RAID control utilities which use the + framework for configuration. This chapter is not a definitive + guide to RAID configurations and only + GEOM-supported RAID + classifications are discussed. After reading this chapter, you will know: @@ -68,8 +69,8 @@ - How to troubleshoot disks attached to the GEOM - framework. + How to troubleshoot disks attached to the + GEOM framework. @@ -82,8 +83,8 @@ - Know how to configure and install a new kernel - (. + Know how to configure and install a new kernel (. @@ -122,18 +123,18 @@ RAID controllers. The GEOM disk subsystem provides software support for disk striping, also known as RAID0, - without the need for a RAID disk + without the need for a RAID disk controller. - In RAID0, data is split into - blocks that are written across all the drives in the array. As - seen in the following illustration, - instead of having to wait on the system to write 256k to one - disk, RAID0 can simultaneously write - 64k to each of the four disks in the array, offering superior I/O - performance. This performance can be enhanced further by using - multiple disk controllers. - + In RAID0, data is split into blocks that + are written across all the drives in the array. As seen in the + following illustration, instead of having to wait on the system + to write 256k to one disk, RAID0 can + simultaneously write 64k to each of the four disks in the array, + offering superior I/O performance. This + performance can be enhanced further by using multiple disk + controllers. + @@ -145,11 +146,12 @@ Each disk in a RAID0 stripe must be of - the same size, since I/O requests are interleaved to read or - write to multiple disks in parallel. + the same size, since I/O requests are + interleaved to read or write to multiple disks in + parallel. - RAID0 does not + RAID0 does not provide any redundancy. This means that if one disk in the array fails, all of the data on the disks is lost. If the data is important, implement a backup strategy that regularly @@ -163,7 +165,8 @@ to control an existing stripe. - Creating a Stripe of Unformatted <acronym>ATA</acronym> Disks + Creating a Stripe of Unformatted <acronym>ATA</acronym> + Disks Load the geom_stripe.ko @@ -203,11 +206,11 @@ Done. This process should create two other devices in - /dev/stripe in - addition to st0. Those include - st0a and - st0c. At this point, a UFS file system - can be created on st0a using + /dev/stripe in addition to + st0. Those include + st0a and st0c. At + this point, a UFS file system can be + created on st0a using newfs: &prompt.root; newfs -U /dev/stripe/st0a @@ -218,30 +221,31 @@ Done. - To manually mount the created disk stripe: + To manually mount the created disk stripe: - &prompt.root; mount /dev/stripe/st0a /mnt + &prompt.root; mount /dev/stripe/st0a /mnt - To mount this striped file system automatically during the - boot process, place the volume information in - /etc/fstab. In this example, a permanent - mount point, named stripe, is - created: + To mount this striped file system automatically during + the boot process, place the volume information in + /etc/fstab. In this example, a + permanent mount point, named stripe, is + created: - &prompt.root; mkdir /stripe + &prompt.root; mkdir /stripe &prompt.root; echo "/dev/stripe/st0a /stripe ufs rw 2 2" \ - >> /etc/fstab - +>> /etc/fstab + - - The geom_stripe.ko module must also be - automatically loaded during system initialization, by adding a - line to /boot/loader.conf: + + The geom_stripe.ko module must also + be automatically loaded during system initialization, by + adding a line to + /boot/loader.conf: - &prompt.root; echo 'geom_stripe_load="YES"' >> /boot/loader.conf - + &prompt.root; echo 'geom_stripe_load="YES"' >> /boot/loader.conf + @@ -1340,9 +1344,9 @@ Done. <acronym>GEOM</acronym> Gate Network Devices - GEOM supports the remote use of devices, such as disks, - CD-ROMs, and files through the use of the gate utilities. - This is similar to NFS. + GEOM supports the remote use of devices, + such as disks, CD-ROMs, and files through the use of the gate + utilities. This is similar to NFS. To begin, an exports file must be created. This file specifies who is permitted to access the exported resources and