Date: Tue, 29 Apr 2014 17:51:24 +0000 (UTC) From: Dru Lavigne <dru@FreeBSD.org> 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 Message-ID: <201404291751.s3THpOUY058912@svn.freebsd.org>
next in thread | raw e-mail | index | archive | help
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</ </indexterm> <para>Beginning with &os; 7.0, support for journals on - <acronym>UFS</acronym> file systems is - available. The implementation is provided through the - <acronym>GEOM</acronym> subsystem and is configured using - <command>gjournal</command>. Unlike other file system journaling implementations, the + <acronym>UFS</acronym> file systems is available. The + implementation is provided through the <acronym>GEOM</acronym> + subsystem and is configured using <command>gjournal</command>. + Unlike other file system journaling implementations, the <command>gjournal</command> method is block based and not implemented as part of the file system. It is a <acronym>GEOM</acronym> extension.</para> @@ -1638,40 +1638,38 @@ ufsid/486b6fc16926168e N/A ad4s1f</ Updates, which tracks and enforces meta-data updates, and snapshots, which create an image of the file system, a log is stored in disk space specifically for this task. For better - 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.</para> + 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.</para> - <para>The <filename>GENERIC</filename> kernel provides support - for <command>gjournal</command>. To automatically load the + <para>The <filename>GENERIC</filename> kernel provides support for + <command>gjournal</command>. To automatically load the <filename>geom_journal.ko</filename> kernel module at boot time, add the following line to <filename>/boot/loader.conf</filename>:</para> <programlisting>geom_journal_load="YES"</programlisting> - <para>If a custom - kernel is used, ensure the following line is in the kernel configuration - file:</para> + <para>If a custom kernel is used, ensure the following line is in + the kernel configuration file:</para> <programlisting>options GEOM_JOURNAL</programlisting> <para>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, <filename>da4</filename> is a new <acronym>SCSI</acronym> disk:</para> <screen>&prompt.root; <userinput>gjournal load</userinput> &prompt.root; <userinput>gjournal label /dev/<replaceable>da4</replaceable></userinput></screen> - <para>This will load the module and create a <filename>/dev/da4.journal</filename> - device node on + <para>This will load the module and create a + <filename>/dev/da4.journal</filename> device node on <filename>/dev/da4</filename>.</para> - <para>A <acronym>UFS</acronym> file system may now be created on the - journaled device, then mounted on an existing mount point:</para> + <para>A <acronym>UFS</acronym> file system may now be created on + the journaled device, then mounted on an existing mount + point:</para> <screen>&prompt.root; <userinput>newfs -O 2 -J /dev/<replaceable>da4</replaceable>.journal</userinput> &prompt.root; <userinput>mount /dev/<replaceable>da4</replaceable>.journal <replaceable>/mnt</replaceable></userinput></screen> @@ -1679,9 +1677,8 @@ ufsid/486b6fc16926168e N/A ad4s1f</ <note> <para>In the case of several slices, a journal will be created for each individual slice. For instance, if - <filename>ad4s1</filename> and - <filename>ad4s2</filename> are both slices, then - <command>gjournal</command> will create + <filename>ad4s1</filename> and <filename>ad4s2</filename> are + both slices, then <command>gjournal</command> will create <filename>ad4s1.journal</filename> and <filename>ad4s2.journal</filename>.</para> </note> @@ -1689,15 +1686,15 @@ ufsid/486b6fc16926168e N/A ad4s1f</ <para>Journaling may also be enabled on current file systems by using <command>tunefs</command>. However, <emphasis>always</emphasis> make a backup before attempting to - alter an existing file system. In most cases, <command>gjournal</command> - will fail if it is unable to create the journal, but this does - not protect against data loss incurred as a result of misusing - <command>tunefs</command>. Refer to &man.gjournal.8; and - &man.tunefs.8; for more information about these - commands.</para> + alter an existing file system. In most cases, + <command>gjournal</command> will fail if it is unable to create + the journal, but this does not protect against data loss + incurred as a result of misusing <command>tunefs</command>. + Refer to &man.gjournal.8; and &man.tunefs.8; for more + information about these commands.</para> - <para>It is possible to journal the boot disk of a &os; - system. Refer to the article <link + <para>It is possible to journal the boot disk of a &os; system. + Refer to the article <link xlink:href="&url.articles.gjournal-desktop;">Implementing UFS Journaling on a Desktop PC</link> for detailed instructions.</para>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201404291751.s3THpOUY058912>