From owner-svn-doc-head@FreeBSD.ORG Thu Jan 30 03:12:25 2014 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 35ED1158; Thu, 30 Jan 2014 03:12:25 +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)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 1751419F9; Thu, 30 Jan 2014 03:12:25 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id s0U3COkD091711; Thu, 30 Jan 2014 03:12:24 GMT (envelope-from wblock@svn.freebsd.org) Received: (from wblock@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id s0U3COT1091710; Thu, 30 Jan 2014 03:12:24 GMT (envelope-from wblock@svn.freebsd.org) Message-Id: <201401300312.s0U3COT1091710@svn.freebsd.org> From: Warren Block Date: Thu, 30 Jan 2014 03:12:24 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43686 - 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: Thu, 30 Jan 2014 03:12:25 -0000 Author: wblock Date: Thu Jan 30 03:12:24 2014 New Revision: 43686 URL: http://svnweb.freebsd.org/changeset/doc/43686 Log: Whitespace-only fixes, translators please ignore. 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 Thu Jan 30 01:21:13 2014 (r43685) +++ head/en_US.ISO8859-1/books/handbook/geom/chapter.xml Thu Jan 30 03:12:24 2014 (r43686) @@ -4,15 +4,24 @@ $FreeBSD$ --> - - GEOM: Modular Disk Transformation Framework + + + + GEOM: Modular Disk Transformation Framework + - TomRhodesWritten by + + + Tom + Rhodes + + Written by + - - Synopsis @@ -25,7 +34,8 @@ This chapter covers the use of disks under the GEOM - framework in &os;. This includes the major RAID + framework in &os;. This includes the major RAID control utilities which use the framework for configuration. This chapter will not go into in depth discussion on how GEOM handles or controls I/O, the underlying subsystem, or code. @@ -64,11 +74,13 @@ - Understand how &os; treats disk devices. + Understand how &os; treats disk + devices. - Know how to configure and install a new &os; kernel. + Know how to configure and install a new + &os; kernel. @@ -78,22 +90,34 @@ GEOM permits access and control to classes, such as Master Boot Records and BSD labels, through the use - of providers, or the special files in /dev. By supporting various - software RAID configurations, GEOM - transparently provides access to the operating system and - operating system utilities. + of providers, or the special files in /dev. + By supporting various software RAID + configurations, GEOM transparently provides access to the + operating system and operating system utilities. - RAID0 - Striping + + RAID0 - Striping + - TomRhodesWritten by - MurrayStokely + + + Tom + Rhodes + + Written by + + + + + Murray + Stokely + + - - GEOM @@ -142,7 +166,8 @@ Ensure that a suitable mount point exists. If this volume will become a root partition, then temporarily use - another mount point such as /mnt: + another mount point such as + /mnt: &prompt.root; mkdir /mnt @@ -192,8 +217,9 @@ Done. 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: + /etc/fstab. In this example, a permanent + mount point, named stripe, is + created: &prompt.root; mkdir /stripe &prompt.root; echo "/dev/stripe/st0a /stripe ufs rw 2 2" \ @@ -407,7 +433,8 @@ Done. are identical, it does not matter which is selected to boot. - See the Troubleshooting + See the Troubleshooting section if there are problems booting. Powering down and disconnecting the original ada0 disk will allow it to be kept as an offline backup. @@ -789,9 +816,11 @@ mountroot> &prompt.root; gmirror forget gm0 - Any old metadata should be cleared from the replacement - disk. Then the disk, ada4 - for this example, is inserted into the mirror: + Any old metadata should be + cleared from the + replacement disk. Then the disk, + ada4 for this example, is inserted into + the mirror: &prompt.root; gmirror insert gm0 /dev/ada4 @@ -812,12 +841,19 @@ mountroot> - Software <acronym>RAID</acronym> Devices + + Software <acronym>RAID</acronym> Devices + - WarrenBlockOriginally contributed by + + + Warren + Block + + Originally contributed by + - GEOM @@ -1116,20 +1152,46 @@ raid/r0 OPTIMAL ada0 (ACTIVE (ACTIVE)) - <acronym>RAID</acronym>3 - Byte-level Striping with - Dedicated Parity + + + <acronym>RAID</acronym>3 - Byte-level Striping with + Dedicated Parity + - MarkGladmanWritten by - DanielGerzo + + + Mark + Gladman + + Written by + + + + + Daniel + Gerzo + + + - TomRhodesBased on documentation by - MurrayStokely + + + Tom + Rhodes + + Based on documentation by + + + + + Murray + Stokely + + - - GEOM @@ -1294,7 +1356,8 @@ Done. ggate0 &prompt.root; mount /dev/ggate0 /mnt - The device may now be accessed through the /mnt mount point. + The device may now be accessed through the + /mnt mount point. However, this will fail if the device is currently mounted @@ -1362,18 +1425,18 @@ ggate0 Permanent labels can be a generic or a file system label. Permanent file system labels can be created with &man.tunefs.8; or &man.newfs.8;. These types of labels are - created in a sub-directory of /dev, and will be named - according to the file system type. For example, + created in a sub-directory of /dev, and + will be named according to the file system type. For example, UFS2 file system labels will be created in - /dev/ufs. Generic - permanent labels can be created with glabel - label. These are not file system specific and - will be created in /dev/label. + /dev/ufs. Generic permanent labels can + be created with glabel label. These are + not file system specific and will be created in + /dev/label. Temporary labels are destroyed at the next reboot. These - labels are created in /dev/label and are suited to - experimentation. A temporary label can be created using - glabel create. + labels are created in /dev/label and are + suited to experimentation. A temporary label can be created + using glabel create. @@ -1389,8 +1452,8 @@ ggate0 corruption. - A label should now exist in /dev/ufs which may be added - to /etc/fstab: + A label should now exist in /dev/ufs + which may be added to /etc/fstab: /dev/ufs/home /home ufs rw 2 2 @@ -1612,7 +1675,8 @@ ufsid/486b6fc16926168e N/A ad4s1ftunefs. It is also possible to journal the boot disk of a &os; - system. Refer to the article Implementing UFS + system. Refer to the article Implementing UFS Journaling on a Desktop PC for detailed instructions.