MySQL Lists are EOL. Please join:

List:Commits« Previous MessageNext Message »
From:paul Date:December 21 2007 4:26pm
Subject:svn commit - mysqldoc@docsrva: r9434 - in trunk: . dynamic-docs/changelog refman-4.1 refman-5.0 refman-5.1 refman-6.0
View as plain text  
Author: paul
Date: 2007-12-21 17:26:27 +0100 (Fri, 21 Dec 2007)
New Revision: 9434

Log:
 r28363@frost:  paul | 2007-12-21 10:20:04 -0600
 Added notes about table corruption info now written to error log.
 (WL#3951)


Modified:
   trunk/dynamic-docs/changelog/mysqld-1.xml
   trunk/refman-4.1/errors-problems.xml
   trunk/refman-4.1/installing.xml
   trunk/refman-5.0/errors-problems.xml
   trunk/refman-5.0/extending-mysql.xml
   trunk/refman-5.1/errors-problems-core.xml
   trunk/refman-5.1/extending-mysql.xml
   trunk/refman-6.0/errors-problems.xml
   trunk/refman-6.0/extending-mysql.xml

Property changes on: trunk
___________________________________________________________________
Name: svk:merge
   - 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:34416
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:28344
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:22582
   + 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:34416
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:28363
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:22582


Modified: trunk/dynamic-docs/changelog/mysqld-1.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-1.xml	2007-12-21 15:27:46 UTC (rev 9433)
+++ trunk/dynamic-docs/changelog/mysqld-1.xml	2007-12-21 16:26:27 UTC (rev 9434)
Changed blocks: 1, Lines Added: 27, Lines Deleted: 0; 1022 bytes

@@ -3710,4 +3710,31 @@
 
   </logentry>
 
+  <logentry entrytype="feature">
+
+    <tags>
+      <manual type="MyISAM"/>
+      <manual type="logging"/>
+      <manual type="table corruption"/>
+    </tags>
+
+    <versions>
+      <version ver="6.0.4"/>
+    </versions>
+
+    <message>
+
+      <para>
+        When the server detects <literal>MyISAM</literal> table
+        corruption, it now writes additional information to the error
+        log, such as the name and line number of the source file, and
+        the list of threads accessing the table. Example: <literal>Got
+        an error from thread_id=1, mi_dynrec.c:368</literal>. This is
+        useful information to include in bug reports.
+      </para>
+
+    </message>
+
+  </logentry>
+
 </changelog>


Modified: trunk/refman-4.1/errors-problems.xml
===================================================================
--- trunk/refman-4.1/errors-problems.xml	2007-12-21 15:27:46 UTC (rev 9433)
+++ trunk/refman-4.1/errors-problems.xml	2007-12-21 16:26:27 UTC (rev 9434)
Changed blocks: 1, Lines Added: 26, Lines Deleted: 0; 1381 bytes

@@ -2372,6 +2372,32 @@
 
       </section>
 
+      <section id="table-corruption">
+
+        <title>Table-Corruption Issues</title>
+
+        <para>
+          If you have started <command>mysqld</command> with
+          <option>--myisam-recover</option>, MySQL automatically checks
+          and tries to repair <literal>MyISAM</literal> tables if they
+          are marked as 'not closed properly' or 'crashed'. If this
+          happens, MySQL writes an entry in the
+          <literal>hostname.err</literal> file <literal>'Warning:
+          Checking table ...'</literal> which is followed by
+          <literal>Warning: Repairing table</literal> if the table needs
+          to be repaired. If you get a lot of these errors, without
+          <command>mysqld</command> having died unexpectedly just
+          before, then something is wrong and needs to be investigated
+          further.
+        </para>
+
+        <para>
+          See also <xref linkend="server-options"/>, and
+          <xref linkend="reproducible-test-case"/>.
+        </para>
+
+      </section>
+
     </section>
 
     <section id="installation-issues">


Modified: trunk/refman-4.1/installing.xml
===================================================================
--- trunk/refman-4.1/installing.xml	2007-12-21 15:27:46 UTC (rev 9433)
+++ trunk/refman-4.1/installing.xml	2007-12-21 16:26:27 UTC (rev 9434)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 679 bytes

@@ -20120,7 +20120,7 @@
 
         <para>
           If you have started <command>mysqld</command> with
-          <literal>myisam-recover</literal>, MySQL automatically checks
+          <option>--myisam-recover</option>, MySQL automatically checks
           and tries to repair <literal>MyISAM</literal> tables if they
           are marked as 'not closed properly' or 'crashed'. If this
           happens, MySQL writes an entry in the


Modified: trunk/refman-5.0/errors-problems.xml
===================================================================
--- trunk/refman-5.0/errors-problems.xml	2007-12-21 15:27:46 UTC (rev 9433)
+++ trunk/refman-5.0/errors-problems.xml	2007-12-21 16:26:27 UTC (rev 9434)
Changed blocks: 1, Lines Added: 26, Lines Deleted: 0; 1381 bytes

@@ -2289,6 +2289,32 @@
 
       </section>
 
+      <section id="table-corruption">
+
+        <title>Table-Corruption Issues</title>
+
+        <para>
+          If you have started <command>mysqld</command> with
+          <option>--myisam-recover</option>, MySQL automatically checks
+          and tries to repair <literal>MyISAM</literal> tables if they
+          are marked as 'not closed properly' or 'crashed'. If this
+          happens, MySQL writes an entry in the
+          <literal>hostname.err</literal> file <literal>'Warning:
+          Checking table ...'</literal> which is followed by
+          <literal>Warning: Repairing table</literal> if the table needs
+          to be repaired. If you get a lot of these errors, without
+          <command>mysqld</command> having died unexpectedly just
+          before, then something is wrong and needs to be investigated
+          further.
+        </para>
+
+        <para>
+          See also <xref linkend="server-options"/>, and
+          <xref linkend="reproducible-test-case"/>.
+        </para>
+
+      </section>
+
     </section>
 
     <section id="installation-issues">


Modified: trunk/refman-5.0/extending-mysql.xml
===================================================================
--- trunk/refman-5.0/extending-mysql.xml	2007-12-21 15:27:46 UTC (rev 9433)
+++ trunk/refman-5.0/extending-mysql.xml	2007-12-21 16:26:27 UTC (rev 9434)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 692 bytes

@@ -3317,7 +3317,7 @@
 
         <para>
           If you have started <command>mysqld</command> with
-          <literal>myisam-recover</literal>, MySQL automatically checks
+          <option>--myisam-recover</option>, MySQL automatically checks
           and tries to repair <literal>MyISAM</literal> tables if they
           are marked as 'not closed properly' or 'crashed'. If this
           happens, MySQL writes an entry in the


Modified: trunk/refman-5.1/errors-problems-core.xml
===================================================================
--- trunk/refman-5.1/errors-problems-core.xml	2007-12-21 15:27:46 UTC (rev 9433)
+++ trunk/refman-5.1/errors-problems-core.xml	2007-12-21 16:26:27 UTC (rev 9434)
Changed blocks: 1, Lines Added: 26, Lines Deleted: 0; 1396 bytes

@@ -2293,6 +2293,32 @@
 
       </section>
 
+      <section id="table-corruption">
+
+        <title>Table-Corruption Issues</title>
+
+        <para>
+          If you have started <command>mysqld</command> with
+          <option>--myisam-recover</option>, MySQL automatically checks
+          and tries to repair <literal>MyISAM</literal> tables if they
+          are marked as 'not closed properly' or 'crashed'. If this
+          happens, MySQL writes an entry in the
+          <literal>hostname.err</literal> file <literal>'Warning:
+          Checking table ...'</literal> which is followed by
+          <literal>Warning: Repairing table</literal> if the table needs
+          to be repaired. If you get a lot of these errors, without
+          <command>mysqld</command> having died unexpectedly just
+          before, then something is wrong and needs to be investigated
+          further.
+        </para>
+
+        <para>
+          See also <xref linkend="server-options"/>, and
+          <xref linkend="reproducible-test-case"/>.
+        </para>
+
+      </section>
+
     </section>
 
     <section id="installation-issues">


Modified: trunk/refman-5.1/extending-mysql.xml
===================================================================
--- trunk/refman-5.1/extending-mysql.xml	2007-12-21 15:27:46 UTC (rev 9433)
+++ trunk/refman-5.1/extending-mysql.xml	2007-12-21 16:26:27 UTC (rev 9434)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 692 bytes

@@ -5614,7 +5614,7 @@
 
         <para>
           If you have started <command>mysqld</command> with
-          <literal>myisam-recover</literal>, MySQL automatically checks
+          <option>--myisam-recover</option>, MySQL automatically checks
           and tries to repair <literal>MyISAM</literal> tables if they
           are marked as 'not closed properly' or 'crashed'. If this
           happens, MySQL writes an entry in the


Modified: trunk/refman-6.0/errors-problems.xml
===================================================================
--- trunk/refman-6.0/errors-problems.xml	2007-12-21 15:27:46 UTC (rev 9433)
+++ trunk/refman-6.0/errors-problems.xml	2007-12-21 16:26:27 UTC (rev 9434)
Changed blocks: 1, Lines Added: 36, Lines Deleted: 0; 1850 bytes

@@ -2282,6 +2282,42 @@
 
       </section>
 
+      <section id="table-corruption">
+
+        <title>Table-Corruption Issues</title>
+
+        <para>
+          If you have started <command>mysqld</command> with
+          <option>--myisam-recover</option>, MySQL automatically checks
+          and tries to repair <literal>MyISAM</literal> tables if they
+          are marked as 'not closed properly' or 'crashed'. If this
+          happens, MySQL writes an entry in the
+          <literal>hostname.err</literal> file <literal>'Warning:
+          Checking table ...'</literal> which is followed by
+          <literal>Warning: Repairing table</literal> if the table needs
+          to be repaired. If you get a lot of these errors, without
+          <command>mysqld</command> having died unexpectedly just
+          before, then something is wrong and needs to be investigated
+          further.
+        </para>
+
+        <para>
+          As of MySQL 6.0.4, when the server detects
+          <literal>MyISAM</literal> table corruption, it writes
+          additional information to the error log, such as the name and
+          line number of the source file, and the list of threads
+          accessing the table. Example: <literal>Got an error from
+          thread_id=1, mi_dynrec.c:368 </literal>. This is useful
+          information to include in bug reports.
+        </para>
+
+        <para>
+          See also <xref linkend="server-options"/>, and
+          <xref linkend="reproducible-test-case"/>.
+        </para>
+
+      </section>
+
     </section>
 
     <section id="installation-issues">


Modified: trunk/refman-6.0/extending-mysql.xml
===================================================================
--- trunk/refman-6.0/extending-mysql.xml	2007-12-21 15:27:46 UTC (rev 9433)
+++ trunk/refman-6.0/extending-mysql.xml	2007-12-21 16:26:27 UTC (rev 9434)
Changed blocks: 2, Lines Added: 11, Lines Deleted: 1; 1430 bytes

@@ -5597,7 +5597,7 @@
 
         <para>
           If you have started <command>mysqld</command> with
-          <literal>myisam-recover</literal>, MySQL automatically checks
+          <option>--myisam-recover</option>, MySQL automatically checks
           and tries to repair <literal>MyISAM</literal> tables if they
           are marked as 'not closed properly' or 'crashed'. If this
           happens, MySQL writes an entry in the

@@ -5611,6 +5611,16 @@
         </para>
 
         <para>
+          As of MySQL 6.0.4, when the server detects
+          <literal>MyISAM</literal> table corruption, it writes
+          additional information to the error log, such as the name and
+          line number of the source file, and the list of threads
+          accessing the table. Example: <literal>Got an error from
+          thread_id=1, mi_dynrec.c:368 </literal>. This is useful
+          information to include in bug reports.
+        </para>
+
+        <para>
           It is not a good sign if <command>mysqld</command> did die
           unexpectedly, but in this case, you should not investigate the
           <literal>Checking table...</literal> messages, but instead try


Thread
svn commit - mysqldoc@docsrva: r9434 - in trunk: . dynamic-docs/changelog refman-4.1 refman-5.0 refman-5.1 refman-6.0paul21 Dec