<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0">
<channel>
<title><![CDATA[向东博客 专注WEB应用 构架之美 --- 构架之美，在于尽态极妍 | 应用之美，在于药到病除]]></title> 
<link>http://www.jackxiang.com/index.php</link> 
<description><![CDATA[赢在IT，Playin' with IT,Focus on Killer Application,Marketing Meets Technology.]]></description> 
<language>zh-cn</language> 
<copyright><![CDATA[向东博客 专注WEB应用 构架之美 --- 构架之美，在于尽态极妍 | 应用之美，在于药到病除]]></copyright>
<item>
<link>http://www.jackxiang.com/post//</link>
<title><![CDATA[MYSQL的INNODB表的修复]]></title> 
<author>jack &lt;xdy108@126.com&gt;</author>
<category><![CDATA[WEB2.0]]></category>
<pubDate>Sat, 25 Sep 2010 11:45:38 +0000</pubDate> 
<guid>http://www.jackxiang.com/post//</guid> 
<description>
<![CDATA[ 
	<br/><br/><br/>通常使用的 MyISAM 表可以用上面提到的恢复方法来完成。如果是索引坏了，可以用 myisamchk 工具来重建索引。而对于 Innodb 表来说，就没这么直接了，因为它把所有的表都保存在一个表空间了。不过 Innodb 有一个检查机制叫模糊检查点，只要保存了日志文件，就能根据日志文件来修复错误。可以在 my.cnf 文件中，增加以下参数，让 mysqld 在启动时自动检查日志文件：<br/><br/><br/><div class="code">innodb_force_recovery = 4</div><br/><br/>要保存了日志文件！！！！<br/><div class="code">100925 19:18:46&nbsp;&nbsp;mysqld started<br/>100925 19:18:46&nbsp;&nbsp;InnoDB: Database was not shut down normally!<br/>InnoDB: Starting crash recovery.<br/>InnoDB: Reading tablespace information from the .ibd files...<br/>InnoDB: Restoring possible half-written data pages from the doublewrite<br/>InnoDB: buffer...<br/>100925 19:18:46&nbsp;&nbsp;InnoDB: Starting log scan based on checkpoint at<br/>InnoDB: log sequence number 94 1409777360.<br/>InnoDB: Doing recovery: scanned up to log sequence number 94 1409777360<br/>100925 19:18:46&nbsp;&nbsp;InnoDB: Error: page 4734977 log sequence number 94 1537001576<br/>InnoDB: is in the future! Current system log sequence number 94 1409777360.<br/>InnoDB: Your database may be corrupt or you may have copied the InnoDB<br/>InnoDB: tablespace but not the InnoDB log files. See<br/>InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html<br/>InnoDB: for more information.<br/>100925 19:18:46&nbsp;&nbsp;InnoDB: Error: page 4734991 log sequence number 94 1668918230<br/>InnoDB: is in the future! Current system log sequence number 94 1409777360.<br/>InnoDB: Your database may be corrupt or you may have copied the InnoDB<br/>InnoDB: tablespace but not the InnoDB log files.</div><br/>我考，没有InnoDb日志文件，彻底挂了！！！
]]>
</description>
</item><item>
<link>http://www.jackxiang.com/post//#blogcomment</link>
<title><![CDATA[[评论] MYSQL的INNODB表的修复]]></title> 
<author> &lt;user@domain.com&gt;</author>
<category><![CDATA[评论]]></category>
<pubDate>Thu, 01 Jan 1970 00:00:00 +0000</pubDate> 
<guid>http://www.jackxiang.com/post//#blogcomment</guid> 
<description>
<![CDATA[ 
	
]]>
</description>
</item>
</channel>
</rss>