doc-el commit 844:173dbb3990cd - Add "kernel panic relaxing" pat...

[freebsd-doc-el at lists.hellug.gr]

changeset:      844:173dbb3990cd
user:           Manolis Kiagias <sonicy at otenet.gr>
date:           2008-09-28 14:49 +0300
details:        http://hg.hellug.gr/freebsd/doc-el/?cmd=changeset;node=173dbb3990cd

description:
	Add "kernel panic relaxing" patch for gjournal-desktop article

diffs (31 lines):

diff -r 8e7f81d3581f -r 173dbb3990cd en_US.ISO8859-1/articles/gjournal-desktop/article.sgml
--- a/en_US.ISO8859-1/articles/gjournal-desktop/article.sgml	Sun Sep 28 13:36:04 2008 +0300
+++ b/en_US.ISO8859-1/articles/gjournal-desktop/article.sgml	Sun Sep 28 14:49:23 2008 +0300
@@ -185,6 +185,17 @@
       video editing) may need more.  A kernel panic will occur if the
       journal space is exhausted before it has a chance to be
       committed.</para>
+
+    <note>
+      <para>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&nbsp;Gb RAM, create an
+	approximately 3.3&nbsp;Gb journal provider. (Multiply your
+	RAM size by 3.3 to obtain the size of the journal).</para>
+    </note>
 
     <para>For more information about journaling, please read the manual
       page of &man.gjournal.8;.</para> 
@@ -520,7 +531,8 @@
 	    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.</para>
+	    partition for the journal.  See the note in the <link
+	      linkend="understanding-journaling">Understanding Journaling</link> section.</para>
 	</answer>
       </qandaentry>