Source string Read only

(itstool) path: answer/screen

55/550
Context English State
Troubleshooting Journaling
The following section covers frequently asked questions regarding problems related to journaling.
I am getting kernel panics during periods of high disk activity. How is this related to journaling?
The journal probably fills up before it has a chance to get committed (flushed) to disk. Keep in mind the size of the journal depends on the usage load, and not the size of the data provider. If your disk activity is high, you need a larger partition for the journal. See the note in the <link linkend="understanding-journaling">Understanding Journaling</link> section.
I made some mistake during configuration, and I cannot boot normally now. Can this be fixed some way?
You either forgot (or misspelled) the entry in <filename>/boot/loader.conf</filename>, or there are errors in your <filename>/etc/fstab</filename> file. These are usually easy to fix. Press <keycap>Enter</keycap> to get to the default single user shell. Then locate the root of the problem:
<prompt>#</prompt> <userinput>cat /boot/loader.conf</userinput>
If the <literal>geom_journal_load</literal> entry is missing or misspelled, the journaled devices are never created. Load the module manually, mount all partitions, and continue with multi-user boot:
<prompt>#</prompt> <userinput>gjournal load</userinput>

GEOM_JOURNAL: Journal 2948326772: ad0s1g contains journal.
GEOM_JOURNAL: Journal 3193218002: ad0s1h contains journal.
GEOM_JOURNAL: Journal 3193218002: ad0s1d contains data.
GEOM_JOURNAL: Journal ad0s1d clean.
GEOM_JOURNAL: Journal 2948326772: ad0s1f contains data.
GEOM_JOURNAL: Journal ad0s1f clean.

<prompt>#</prompt> <userinput>mount -a</userinput>
<prompt>#</prompt> <userinput>exit</userinput>
<emphasis>(boot continues)</emphasis>
If, on the other hand, this entry is correct, have a look at <filename>/etc/fstab</filename>. You will probably find a misspelled or missing entry. In this case, mount all remaining partitions by hand and continue with the multi-user boot.
Can I remove journaling and return to my standard file system with Soft Updates?
Sure. Use the following procedure, which reverses the changes. The partitions you created for the journal providers can then be used for other purposes, if you so wish.
Login as <systemitem class="username">root</systemitem> and switch to single user mode:
Unmount the journaled partitions:
Synchronize the journals:
<prompt>#</prompt> <userinput>gjournal sync</userinput>
Stop the journaling providers:
<prompt>#</prompt> <userinput>gjournal stop ad0s1d.journal</userinput>
<prompt>#</prompt> <userinput>gjournal stop ad0s1f.journal</userinput>
Clear journaling metadata from all the devices used:
<prompt>#</prompt> <userinput>gjournal clear ad0s1d</userinput>
<prompt>#</prompt> <userinput>gjournal clear ad0s1f</userinput>
<prompt>#</prompt> <userinput>gjournal clear ad0s1g</userinput>
<prompt>#</prompt> <userinput>gjournal clear ad0s1h</userinput>
Clear the file system journaling flag, and restore the Soft Updates flag:
<prompt>#</prompt> <userinput>tunefs -J disable -n enable ad0s1d</userinput>

tunefs: gjournal cleared
tunefs: soft updates set

<prompt>#</prompt> <userinput>tunefs -J disable -n enable ad0s1f</userinput>

tunefs: gjournal cleared
tunefs: soft updates set
Remount the old devices by hand:
<prompt>#</prompt> <userinput>mount -o rw /dev/ad0s1d /var</userinput>
<prompt>#</prompt> <userinput>mount -o rw /dev/ad0s1f /usr</userinput>
Edit <filename>/etc/fstab</filename> and restore it to its original state:
/dev/ad0s1f /usr ufs rw 2 2
/dev/ad0s1d /var ufs rw 2 2
Finally, edit <filename>/boot/loader.conf</filename>, remove the entry that loads the <literal>geom_journal</literal> module and reboot.
Further Reading
Journaling is a fairly new feature of FreeBSD, and as such, it is not very well documented yet. You may however find the following additional references useful:
A <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/handbook/geom-gjournal.html">new section on journaling</link> is now part of the FreeBSD Handbook.
<link xlink:href="https://lists.freebsd.org/pipermail/freebsd-current/2006-June/064043.html">This post</link> in <link xlink:href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-current">freebsd-current</link> by <citerefentry><refentrytitle>gjournal</refentrytitle><manvolnum>8</manvolnum></citerefentry>'s developer, Paweł Jakub Dawidek <email>pjd@FreeBSD.org</email>.

Loading…

No matching activity found.

Browse all component changes

Things to check

Multiple failing checks

The translations in several languages have failing checks

Reset

Glossary

English English
No related strings found in the glossary.

Source information

Source string comment

(itstool) path: answer/screen

Flags
no-wrap, read-only
Source string location
article.translate.xml:592
String age
a year ago
Source string age
a year ago
Translation file
articles/gjournal-desktop.pot, string 118