Gjournal - Revision history

Tykling at 02:38, 11 November 2010

2010-11-11T02:38:32Z

← Older revision		Revision as of 02:38, 11 November 2010
Line 1:		Line 1:
	__FORCETOC__		__FORCETOC__
	[[category:GEOM Related]]		[[category:GEOM Related]]
			'''I don't actually use gjournal anymore, we have ZFS now and for everything else, UFS has it's own journalling.''' --[[User:Tykling\|Tykling]] 02:38, 11 November 2010 (UTC)

	== Introduction ==		== Introduction ==
	Journaling file systems are designed to write any pending io writes to a journal (log) before actually writing the metadata and actual data to the disk. If a power outage or similar occurs, the journal can be used to re-run the transactions that were lost - or at least check that the data was written as intended. gjournal means the end of having to run fsck after a crash, since you know the data on the disk is always in sync, something most admins will gladly welcome.		Journaling file systems are designed to write any pending io writes to a journal (log) before actually writing the metadata and actual data to the disk. If a power outage or similar occurs, the journal can be used to re-run the transactions that were lost - or at least check that the data was written as intended. gjournal means the end of having to run fsck after a crash, since you know the data on the disk is always in sync, something most admins will gladly welcome.

Tykling at 13:00, 23 February 2009

2009-02-23T13:00:18Z

← Older revision		Revision as of 13:00, 23 February 2009
Line 1:		Line 1:
	__FORCETOC__		__FORCETOC__
	[[category:GEOM Related]]		[[category:GEOM Related]]
			== Introduction ==
			Journaling file systems are designed to write any pending io writes to a journal (log) before actually writing the metadata and actual data to the disk. If a power outage or similar occurs, the journal can be used to re-run the transactions that were lost - or at least check that the data was written as intended. gjournal means the end of having to run fsck after a crash, since you know the data on the disk is always in sync, something most admins will gladly welcome.

	== Journaling system partitions on the boot disk ==		== Journaling system partitions on the boot disk ==
	Sysinstall doesn't currently have a way to install FreeBSD to a journaled device. You will need to create extra partitions to contain the journals in the partitioning part of the sysinstall process. The handbook does not recommend journaling small file systems, so /usr and /var are candidates for journaling on a default partition scheme. The recommended approach is to create extra swap partitions to contain the journals in sysinstall, and after the installation is completed to remove the extra swap partitions from ''/etc/fstab'' so they won't be used for swap, and reboot. You need one journal partition per partition you want journaling enabled on, so in the default case two extra swap partitions should be created. The size depends on the expected load on the file system, not the size of the file system. A very busy file system needs to have a journal 3.3x the size of available system memory. More on journal sizes [[http://www.freebsd.org/doc/en_US.ISO8859-1/articles/gjournal-desktop/understanding-journaling.html here]]. So, step by step:		Sysinstall doesn't currently have a way to install FreeBSD to a journaled device. You will need to create extra partitions to contain the journals in the partitioning part of the sysinstall process. The handbook does not recommend journaling small file systems, so /usr and /var are candidates for journaling on a default partition scheme. The recommended approach is to create extra swap partitions to contain the journals in sysinstall, and after the installation is completed to remove the extra swap partitions from ''/etc/fstab'' so they won't be used for swap, and reboot. You need one journal partition per partition you want journaling enabled on, so in the default case two extra swap partitions should be created. The size depends on the expected load on the file system, not the size of the file system. A very busy file system needs to have a journal 3.3x the size of available system memory. More on journal sizes [[http://www.freebsd.org/doc/en_US.ISO8859-1/articles/gjournal-desktop/understanding-journaling.html here]]. So, step by step:

Tykling at 12:55, 23 February 2009

2009-02-23T12:55:49Z

← Older revision		Revision as of 12:55, 23 February 2009
Line 1:		Line 1:
	__FORCETOC__		__FORCETOC__
			[[category:GEOM Related]]
	== Journaling system partitions on the boot disk ==		== Journaling system partitions on the boot disk ==
	Sysinstall doesn't currently have a way to install FreeBSD to a journaled device. You will need to create extra partitions to contain the journals in the partitioning part of the sysinstall process. The handbook does not recommend journaling small file systems, so /usr and /var are candidates for journaling on a default partition scheme. The recommended approach is to create extra swap partitions to contain the journals in sysinstall, and after the installation is completed to remove the extra swap partitions from ''/etc/fstab'' so they won't be used for swap, and reboot. You need one journal partition per partition you want journaling enabled on, so in the default case two extra swap partitions should be created. The size depends on the expected load on the file system, not the size of the file system. A very busy file system needs to have a journal 3.3x the size of available system memory. More on journal sizes [[http://www.freebsd.org/doc/en_US.ISO8859-1/articles/gjournal-desktop/understanding-journaling.html here]]. So, step by step:		Sysinstall doesn't currently have a way to install FreeBSD to a journaled device. You will need to create extra partitions to contain the journals in the partitioning part of the sysinstall process. The handbook does not recommend journaling small file systems, so /usr and /var are candidates for journaling on a default partition scheme. The recommended approach is to create extra swap partitions to contain the journals in sysinstall, and after the installation is completed to remove the extra swap partitions from ''/etc/fstab'' so they won't be used for swap, and reboot. You need one journal partition per partition you want journaling enabled on, so in the default case two extra swap partitions should be created. The size depends on the expected load on the file system, not the size of the file system. A very busy file system needs to have a journal 3.3x the size of available system memory. More on journal sizes [[http://www.freebsd.org/doc/en_US.ISO8859-1/articles/gjournal-desktop/understanding-journaling.html here]]. So, step by step:

Tykling at 14:35, 22 February 2009

2009-02-22T14:35:59Z

← Older revision		Revision as of 14:35, 22 February 2009
Line 1:		Line 1:
			__FORCETOC__
	== Journaling system partitions on the boot disk ==		== Journaling system partitions on the boot disk ==
	Sysinstall doesn't currently have a way to install FreeBSD to a journaled device. You will need to create extra partitions to contain the journals in the partitioning part of the sysinstall process. The handbook does not recommend journaling small file systems, so /usr and /var are candidates for journaling on a default partition scheme. The recommended approach is to create extra swap partitions to contain the journals in sysinstall, and after the installation is completed to remove the extra swap partitions from ''/etc/fstab'' so they won't be used for swap, and reboot. You need one journal partition per partition you want journaling enabled on, so in the default case two extra swap partitions should be created. The size depends on the expected load on the file system, not the size of the file system. A very busy file system needs to have a journal 3.3x the size of available system memory. More on journal sizes [[http://www.freebsd.org/doc/en_US.ISO8859-1/articles/gjournal-desktop/understanding-journaling.html here]]. So, step by step:		Sysinstall doesn't currently have a way to install FreeBSD to a journaled device. You will need to create extra partitions to contain the journals in the partitioning part of the sysinstall process. The handbook does not recommend journaling small file systems, so /usr and /var are candidates for journaling on a default partition scheme. The recommended approach is to create extra swap partitions to contain the journals in sysinstall, and after the installation is completed to remove the extra swap partitions from ''/etc/fstab'' so they won't be used for swap, and reboot. You need one journal partition per partition you want journaling enabled on, so in the default case two extra swap partitions should be created. The size depends on the expected load on the file system, not the size of the file system. A very busy file system needs to have a journal 3.3x the size of available system memory. More on journal sizes [[http://www.freebsd.org/doc/en_US.ISO8859-1/articles/gjournal-desktop/understanding-journaling.html here]]. So, step by step:

Tykling at 14:34, 22 February 2009

2009-02-22T14:34:59Z

@@ Line 1: / Line 1: @@
 == Journaling system partitions on the boot disk ==
 Sysinstall doesn't currently have a way to install FreeBSD to a journaled device. You will need to create extra partitions to contain the journals in the partitioning part of the sysinstall process. The handbook does not recommend journaling small file systems, so /usr and /var are candidates for journaling on a default partition scheme. The recommended approach is to create extra swap partitions to contain the journals in sysinstall, and after the installation is completed to remove the extra swap partitions from ''/etc/fstab'' so they won't be used for swap, and reboot. You need one journal partition per partition you want journaling enabled on, so in the default case two extra swap partitions should be created. The size depends on the expected load on the file system, not the size of the file system. A very busy file system needs to have a journal 3.3x the size of available system memory. More on journal sizes [[http://www.freebsd.org/doc/en_US.ISO8859-1/articles/gjournal-desktop/understanding-journaling.html here]]. So, step by step:
-# Install FreeBSD as you normally would, but create an extra swap partition per partition you want journaled. After the install remove the extra swap partitions from fstab. Also add
+# Install FreeBSD as you normally would, but create an extra swap partition per partition you want journaled. After the install remove the extra swap partitions from fstab. Also add ''geom_journal_load="YES"'' to ''/boot/loader.conf'' or the gjournal system will not load at boot time.
 # Use the following approach for each partition you want journaled, substituting the device names for your own of course. In this example the data partition normally mounted on ''/var'' is ''ad0s1d'' and the journal partition is ''da0s1e'':
@@ Line 26: / Line 21: @@
 All that remains is to change the entry for ''/var'' in ''/etc/fstab'' to point to the new journaled device ''/dev/da0s1d.journal''. Remember to also add ''async'' to the mount options, so they read ''rw,async'' instead of just the default ''rw''.

Tykling at 14:24, 22 February 2009

2009-02-22T14:24:59Z

← Older revision		Revision as of 14:24, 22 February 2009
Line 7:		Line 7:
	Sysinstall doesn't currently have a way to install FreeBSD to a journaled device. You will need to create extra partitions to contain the journals in the partitioning part of the sysinstall process. The handbook does not recommend journaling small file systems, so /usr and /var are candidates for journaling on a default partition scheme. The recommended approach is to create extra swap partitions to contain the journals in sysinstall, and after the installation is completed to remove the extra swap partitions from ''/etc/fstab'' so they won't be used for swap, and reboot. You need one journal partition per partition you want journaling enabled on, so in the default case two extra swap partitions should be created. The size depends on the expected load on the file system, not the size of the file system. A very busy file system needs to have a journal 3.3x the size of available system memory. More on journal sizes [[http://www.freebsd.org/doc/en_US.ISO8859-1/articles/gjournal-desktop/understanding-journaling.html here]]. So, step by step:		Sysinstall doesn't currently have a way to install FreeBSD to a journaled device. You will need to create extra partitions to contain the journals in the partitioning part of the sysinstall process. The handbook does not recommend journaling small file systems, so /usr and /var are candidates for journaling on a default partition scheme. The recommended approach is to create extra swap partitions to contain the journals in sysinstall, and after the installation is completed to remove the extra swap partitions from ''/etc/fstab'' so they won't be used for swap, and reboot. You need one journal partition per partition you want journaling enabled on, so in the default case two extra swap partitions should be created. The size depends on the expected load on the file system, not the size of the file system. A very busy file system needs to have a journal 3.3x the size of available system memory. More on journal sizes [[http://www.freebsd.org/doc/en_US.ISO8859-1/articles/gjournal-desktop/understanding-journaling.html here]]. So, step by step:

	# Install FreeBSD as you normally would, but create an extra swap partition per partition you want journaled. After the install remove the extra swap partitions from fstab.		# Install FreeBSD as you normally would, but create an extra swap partition per partition you want journaled. After the install remove the extra swap partitions from fstab. Also add
	# Use the following approach for each partition you want journaled, substituting the device names for your own of course. In this example ~~from [[http://www.freebsd.org/cgi/man.cgi?query=gjournal&sektion=8 the gjournal man page]]~~ the data partition is ad0s1d and the journal partition is da0s1e		# Use the following approach for each partition you want journaled, substituting the device names for your own of course. In this example the data partition normally mounted on ''/var'' is ''ad0s1d'' and the journal partition is ''da0s1e'':

			Start journaling ''da0s1d'' using ''da0s1e'' as the journal partition:
	<pre>		<pre>
	gjournal label da0s1d da0s1e ~~&& \~~		gjournal label -f da0s1d da0s1e
	~~tunefs -J enable -n disable da01sd.journal && \~~
	~~mount -o async /dev/da0s1d.journal /mnt \|\| \~~
	~~mount /dev/da0s1d /mnt~~
	</pre>		</pre>

			Enable journaling on the new filesystem, and disable soft updates:
			<pre>
			tunefs -J enable -n disable da01sd.journal
			</pre>

			Mount the new journaled filesystem:
			<pre>
			mount -o async /dev/da0s1d.journal /var
			</pre>

			All that remains is to change the entry for ''/var'' in ''/etc/fstab'' to point to the new journaled device ''/dev/da0s1d.journal''. Remember to also add ''async'' to the mount options, so they read ''rw,async'' instead of just the default ''rw''.

Tykling: New page: * http://www.freebsd.org/doc/en/books/handbook/geom-gjournal.html * http://www.freebsd.org/cgi/man.cgi?query=gjournal&sektion=8 * http://www.manpages.info/freebsd/newfs.8.html * http://www...

2009-02-22T14:17:39Z

New page: * http://www.freebsd.org/doc/en/books/handbook/geom-gjournal.html * http://www.freebsd.org/cgi/man.cgi?query=gjournal&sektion=8 * http://www.manpages.info/freebsd/newfs.8.html * http://www...

New page

* http://www.freebsd.org/doc/en/books/handbook/geom-gjournal.html
* http://www.freebsd.org/cgi/man.cgi?query=gjournal&sektion=8
* http://www.manpages.info/freebsd/newfs.8.html
* http://www.freebsd.org/doc/en_US.ISO8859-1/articles/gjournal-desktop/

== Journaling system partitions on the boot disk ==
Sysinstall doesn't currently have a way to install FreeBSD to a journaled device. You will need to create extra partitions to contain the journals in the partitioning part of the sysinstall process. The handbook does not recommend journaling small file systems, so /usr and /var are candidates for journaling on a default partition scheme. The recommended approach is to create extra swap partitions to contain the journals in sysinstall, and after the installation is completed to remove the extra swap partitions from ''/etc/fstab'' so they won't be used for swap, and reboot. You need one journal partition per partition you want journaling enabled on, so in the default case two extra swap partitions should be created. The size depends on the expected load on the file system, not the size of the file system. A very busy file system needs to have a journal 3.3x the size of available system memory. More on journal sizes [[http://www.freebsd.org/doc/en_US.ISO8859-1/articles/gjournal-desktop/understanding-journaling.html here]]. So, step by step:

# Install FreeBSD as you normally would, but create an extra swap partition per partition you want journaled. After the install remove the extra swap partitions from fstab.
# Use the following approach for each partition you want journaled, substituting the device names for your own of course. In this example from [[http://www.freebsd.org/cgi/man.cgi?query=gjournal&sektion=8 the gjournal man page]] the data partition is ad0s1d and the journal partition is da0s1e

<pre>
gjournal label da0s1d da0s1e && \
tunefs -J enable -n disable da01sd.journal && \
mount -o async /dev/da0s1d.journal /mnt || \
mount /dev/da0s1d /mnt
</pre>