Source string Read only

(itstool) path: sect2/para
561/5610
Context English State
The amount of disk space you need to reserve for the journal provider depends on the usage load of the file system and not on the size of the data provider. For example on a typical office desktop, a 1 GB journal provider for the <filename>/usr</filename> file system will suffice, while a machine that deals with heavy disk I/O (i.e. video editing) may need more. A kernel panic will occur if the journal space is exhausted before it has a chance to be committed.
The journal sizes suggested here, are highly unlikely to cause problems in typical desktop use (such as web browsing, word processing and playback of media files). If your workload includes intense disk activity, use the following rule for maximum reliability: Your RAM size should fit in 30% of the journal provider's space. For example, if your system has 1 GB RAM, create an approximately 3.3 GB journal provider. (Multiply your RAM size with 3.3 to obtain the size of the journal).
For more information about journaling, please read the manual page of <citerefentry><refentrytitle>gjournal</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
Steps During the Installation of FreeBSD
Reserving Space for Journaling
A typical desktop machine usually has one hard disk that stores both the OS and user data. Arguably, the default partitioning scheme selected by <application>sysinstall</application> is more or less suitable: A desktop machine does not need a large <filename>/var</filename> partition, while <filename>/usr</filename> is allocated the bulk of the disk space, since user data and a lot of packages are installed into its subdirectories.
The default partitioning (the one obtained by pressing <keycap>A</keycap> at the FreeBSD partition editor, called <application>Disklabel</application>) does not leave any unallocated space. Each partition that will be journaled, requires another partition for the journal. Since the <filename>/usr</filename> partition is the largest, it makes sense to shrink this partition slightly, to obtain the space required for journaling.
In our example, an 80 GB disk is used. The following screenshot shows the default partitions created by <application>Disklabel</application> during installation:
_ external ref='disklabel1' md5='__failed__'
If this is more or less what you need, it is very easy to adjust for journaling. Simply use the arrow keys to move the highlight to the <filename>/usr</filename> partition and press <keycap>D</keycap> to delete it.
Now, move the highlight to the disk name at the top of the screen and press <keycap>C</keycap> to create a new partition for <filename>/usr</filename>. This new partition should be smaller by 1 GB (if you intend to journal <filename>/usr</filename> only), or 2 GB (if you intend to journal both <filename>/usr</filename> and <filename>/var</filename>). From the pop-up that appears, opt to create a file system, and type <filename>/usr</filename> as the mount point.
Should you journal the <filename>/var</filename> partition? Normally, journaling makes sense on quite large partitions. You may decide not to journal <filename>/var</filename>, although doing so on a typical desktop will cause no harm. If the file system is lightly used (quite probable for a desktop) you may wish to allocate less disk space for its journal.
In our example, we journal both <filename>/usr</filename> and <filename>/var</filename>. You may of course adjust the procedure to your own needs.
To keep things as easy going as possible, we are going to use <application>sysinstall</application> to create the partitions required for journaling. However, during installation, <application>sysinstall</application> insists on asking a mount point for each partition you create. At this point, you do not have any mount points for the partitions that will hold the journals, and in reality you <emphasis>do not even need them</emphasis>. These are not partitions that we are ever going to mount somewhere.
To avoid these problems with <application>sysinstall</application>, we are going to create the journal partitions as swap space. Swap is never mounted, and <application>sysinstall</application> has no problem creating as many swap partitions as needed. After the first reboot, <filename>/etc/fstab</filename> will have to be edited, and the extra swap space entries removed.
To create the swap, again use the arrow keys to move the highlight to the top of <application>Disklabel</application> screen, so that the disk name itself is highlighted. Then press <keycap>N</keycap>, enter the desired size (<replaceable>1024M</replaceable>), and select <quote>swap space</quote> from the pop-up menu that appears. Repeat for every journal you wish to create. In our example, we create two partitions to provide for the journals of <filename>/usr</filename> and <filename>/var</filename>. The final result is shown in the following screenshot:
_ external ref='disklabel2' md5='__failed__'
When you have completed creating the partitions, we suggest you write down the partition names, and mount points, so you can easily refer to this information during the configuration phase. This will help alleviate mistakes that may damage your installation. The following table shows our notes for the sample configuration:
Partitions and Journals
Partition
Mount Point
Journal
ad0s1d
/var
ad0s1h
ad0s1f
/usr
ad0s1g
Continue the installation as you would normally do. We would however suggest you postpone installation of third party software (packages) until you have completely setup journaling.
Booting for the first time
Your system will come up normally, but you will need to edit <filename>/etc/fstab</filename> and remove the extra swap partitions you created for the journals. Normally, the swap partition you will actually use is the one with the <quote>b</quote> suffix (i.e. ad0s1b in our example). Remove all other swap space entries and reboot so that FreeBSD will stop using them.

Loading…

No matching activity found.

Browse all component changes

Glossary

English English
No related strings found in the glossary.

Source information

Source string comment
(itstool) path: sect2/para
Flags
read-only
Source string location
article.translate.xml:272
String age
a year ago
Source string age
a year ago
Translation file
articles/gjournal-desktop.pot, string 46