- Journaling is not UFS specific.
- Fix spacing that affects the display. - Clean up the note about multiple journals. - Note why you would want the journal on a separate disk. Inspired by: docs/128524
This commit is contained in:
parent
db16cfa41f
commit
2e06265b64
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=36383
1 changed files with 9 additions and 12 deletions
|
@ -706,11 +706,10 @@ ufsid/486b6fc16926168e N/A ad4s1f</screen>
|
|||
<primary>Journaling</primary>
|
||||
</indexterm>
|
||||
|
||||
<para>With the release of &os; 7.0, the long awaited feature
|
||||
of <acronym>UFS</acronym> journals has been implemented. The
|
||||
implementation itself is provided through the
|
||||
<acronym>GEOM</acronym> subsystem and is easily configured
|
||||
via the &man.gjournal.8; utility.</para>
|
||||
<para>With the release of &os; 7.0, the long awaited feature
|
||||
of journals has been implemented. The implementation itself is
|
||||
provided through the <acronym>GEOM</acronym> subsystem and is
|
||||
easily configured via the &man.gjournal.8; utility.</para>
|
||||
|
||||
<para>What is journaling? Journaling capability stores a log of
|
||||
file system transactions, i.e.: changes that make up a complete
|
||||
|
@ -733,7 +732,7 @@ ufsid/486b6fc16926168e N/A ad4s1f</screen>
|
|||
|
||||
<para>To enable support for <command>gjournal</command>, the
|
||||
&os; kernel must have the following option - which is the
|
||||
default on 7.X systems:</para>
|
||||
default on &os; 7.0 and later systems:</para>
|
||||
|
||||
<programlisting>options UFS_GJOURNAL</programlisting>
|
||||
|
||||
|
@ -756,7 +755,7 @@ ufsid/486b6fc16926168e N/A ad4s1f</screen>
|
|||
disk:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>gjournal load</userinput>
|
||||
&prompt.root; <userinput>gjournal label /dev/da4</userinput></screen>
|
||||
&prompt.root; <userinput>gjournal label /dev/da4</userinput></screen>
|
||||
|
||||
<para>At this point, there should be a
|
||||
<devicename>/dev/da4</devicename> device node and a
|
||||
|
@ -766,8 +765,7 @@ ufsid/486b6fc16926168e N/A ad4s1f</screen>
|
|||
<screen>&prompt.root; <userinput>newfs -O 2 -J /dev/da4.journal</userinput></screen>
|
||||
|
||||
<para>The previously issued command will create a
|
||||
<acronym>UFS</acronym>2 file system with journaling being made
|
||||
active.</para>
|
||||
<acronym>UFS</acronym>2 file system on the journaled device.</para>
|
||||
|
||||
<para>Effectively <command>mount</command> the device at the
|
||||
desired point with:</para>
|
||||
|
@ -780,11 +778,10 @@ ufsid/486b6fc16926168e N/A ad4s1f</screen>
|
|||
<devicename>ad4s1</devicename> and <devicename>ad4s2</devicename>
|
||||
are both slices, then <command>gjournal</command> will create
|
||||
<devicename>ad4s1.journal</devicename> and
|
||||
<devicename>ad4s2.journal</devicename>. In the case of the command
|
||||
being run twice, the result will be <quote>journals</quote>.</para>
|
||||
<devicename>ad4s2.journal</devicename>.</para>
|
||||
</note>
|
||||
|
||||
<para>Under some circumstances, keeping the journal on another disk
|
||||
<para>For better performance, keeping the journal on another disk
|
||||
may be desired. For these cases, the journal provider or storage
|
||||
device should be listed after the device to enable journaling
|
||||
on. Journaling may also be enabled on current file systems by
|
||||
|
|
Loading…
Reference in a new issue