<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Innodb crash recovery update</title>
	<atom:link href="http://www.mysqlperformanceblog.com/2007/05/22/innodb-crash-recovery-update/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mysqlperformanceblog.com/2007/05/22/innodb-crash-recovery-update/</link>
	<description>Everything about MySQL Performance</description>
	<lastBuildDate>Sat, 21 Nov 2009 05:23:57 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: MySQL Performance Blog &#187; Innodb Recovery Update - The tricks what failed.</title>
		<link>http://www.mysqlperformanceblog.com/2007/05/22/innodb-crash-recovery-update/comment-page-1/#comment-130697</link>
		<dc:creator>MySQL Performance Blog &#187; Innodb Recovery Update - The tricks what failed.</dc:creator>
		<pubDate>Thu, 24 May 2007 21:06:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/05/22/innodb-crash-recovery-update/#comment-130697</guid>
		<description>[...] I wrote we had been recovering corrupted Innodb Tablespace and it is finally done [...]</description>
		<content:encoded><![CDATA[<p>[...] I wrote we had been recovering corrupted Innodb Tablespace and it is finally done [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: peter</title>
		<link>http://www.mysqlperformanceblog.com/2007/05/22/innodb-crash-recovery-update/comment-page-1/#comment-130202</link>
		<dc:creator>peter</dc:creator>
		<pubDate>Wed, 23 May 2007 08:13:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/05/22/innodb-crash-recovery-update/#comment-130202</guid>
		<description>Toby, 

This is interesting one. As I wrote in the previous post most likely it is Innodb bug because corruption was happening always for the same index in the same set of tables, which is unlikely for hardware bug.   Normally it was OK and easily recoverable but this time crash corrupted page was touched by insert buffer merge process which made this crash terminal :)</description>
		<content:encoded><![CDATA[<p>Toby, </p>
<p>This is interesting one. As I wrote in the previous post most likely it is Innodb bug because corruption was happening always for the same index in the same set of tables, which is unlikely for hardware bug.   Normally it was OK and easily recoverable but this time crash corrupted page was touched by insert buffer merge process which made this crash terminal <img src='http://www.mysqlperformanceblog.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Toby</title>
		<link>http://www.mysqlperformanceblog.com/2007/05/22/innodb-crash-recovery-update/comment-page-1/#comment-130002</link>
		<dc:creator>Toby</dc:creator>
		<pubDate>Wed, 23 May 2007 01:58:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/05/22/innodb-crash-recovery-update/#comment-130002</guid>
		<description>Were you able to find the root cause of the corruption?

Software or hardware? (If the latter, Solaris&#039; ZFS may be prophylactic.)</description>
		<content:encoded><![CDATA[<p>Were you able to find the root cause of the corruption?</p>
<p>Software or hardware? (If the latter, Solaris&#8217; ZFS may be prophylactic.)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
