From owner-svn-doc-all@FreeBSD.ORG Tue Apr 29 17:51:24 2014 Return-Path: Delivered-To: svn-doc-all@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 CAA6A417; Tue, 29 Apr 2014 17:51:24 +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 AB2EA3D6; Tue, 29 Apr 2014 17:51:24 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s3THpOv4058913; Tue, 29 Apr 2014 17:51:24 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s3THpOUY058912; Tue, 29 Apr 2014 17:51:24 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201404291751.s3THpOUY058912@svn.freebsd.org> From: Dru Lavigne Date: Tue, 29 Apr 2014 17:51:24 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r44700 - 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: Tue, 29 Apr 2014 17:51:25 -0000 Author: dru Date: Tue Apr 29 17:51:24 2014 New Revision: 44700 URL: http://svnweb.freebsd.org/changeset/doc/44700 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 Tue Apr 29 17:45:17 2014 (r44699) +++ head/en_US.ISO8859-1/books/handbook/geom/chapter.xml Tue Apr 29 17:51:24 2014 (r44700) @@ -1619,10 +1619,10 @@ ufsid/486b6fc16926168e N/A ad4s1f Beginning with &os; 7.0, support for journals on - UFS file systems is - available. The implementation is provided through the - GEOM subsystem and is configured using - gjournal. Unlike other file system journaling implementations, the + UFS file systems is available. The + implementation is provided through the GEOM + subsystem and is configured using gjournal. + Unlike other file system journaling implementations, the gjournal method is block based and not implemented as part of the file system. It is a GEOM extension. @@ -1638,40 +1638,38 @@ ufsid/486b6fc16926168e N/A ad4s1f + performance, the journal may be stored on another disk. In this + configuration, the journal provider or storage device should be + listed after the device to enable journaling on. - The GENERIC kernel provides support - for gjournal. To automatically load the + The GENERIC kernel provides support for + gjournal. To automatically load the geom_journal.ko kernel module at boot time, add the following line to /boot/loader.conf: geom_journal_load="YES" - If a custom - kernel is used, ensure the following line is in the kernel configuration - file: + If a custom kernel is used, ensure the following line is in + the kernel configuration file: options GEOM_JOURNAL Once the module is loaded, a journal can be created on a new - file system - using the following steps. In this example, + file system using the following steps. In this example, da4 is a new SCSI disk: &prompt.root; gjournal load &prompt.root; gjournal label /dev/da4 - This will load the module and create a /dev/da4.journal - device node on + This will load the module and create a + /dev/da4.journal device node on /dev/da4. - A UFS file system may now be created on the - journaled device, then mounted on an existing mount point: + A UFS file system may now be created on + the journaled device, then mounted on an existing mount + point: &prompt.root; newfs -O 2 -J /dev/da4.journal &prompt.root; mount /dev/da4.journal /mnt @@ -1679,9 +1677,8 @@ ufsid/486b6fc16926168e N/A ad4s1f In the case of several slices, a journal will be created for each individual slice. For instance, if - ad4s1 and - ad4s2 are both slices, then - gjournal will create + ad4s1 and ad4s2 are + both slices, then gjournal will create ad4s1.journal and ad4s2.journal. @@ -1689,15 +1686,15 @@ ufsid/486b6fc16926168e N/A ad4s1fJournaling may also be enabled on current file systems by using tunefs. However, always make a backup before attempting to - alter an existing file system. In most cases, gjournal - will fail if it is unable to create the journal, but this does - not protect against data loss incurred as a result of misusing - tunefs. Refer to &man.gjournal.8; and - &man.tunefs.8; for more information about these - commands. + alter an existing file system. In most cases, + gjournal will fail if it is unable to create + the journal, but this does not protect against data loss + incurred as a result of misusing tunefs. + Refer to &man.gjournal.8; and &man.tunefs.8; for more + information about these commands. - It is possible to journal the boot disk of a &os; - system. Refer to the article It is possible to journal the boot disk of a &os; system. + Refer to the article Implementing UFS Journaling on a Desktop PC for detailed instructions.