<?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"
	>
<channel>
	<title>Comments on: Recovering Innodb table Corruption</title>
	<atom:link href="http://www.mysqlperformanceblog.com/2008/07/04/recovering-innodb-table-corruption/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mysqlperformanceblog.com/2008/07/04/recovering-innodb-table-corruption/</link>
	<description>Everything about MySQL Performance</description>
	<pubDate>Tue, 02 Dec 2008 21:09:53 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: peter</title>
		<link>http://www.mysqlperformanceblog.com/2008/07/04/recovering-innodb-table-corruption/#comment-327094</link>
		<dc:creator>peter</dc:creator>
		<pubDate>Sat, 12 Jul 2008 20:14:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=430#comment-327094</guid>
		<description>Toby,

I ended writing this post well after midnight so I forgot to post the bug.  Posted it now - thanks.
http://bugs.mysql.com/bug.php?id=38078</description>
		<content:encoded><![CDATA[<p>Toby,</p>
<p>I ended writing this post well after midnight so I forgot to post the bug.  Posted it now - thanks.<br />
<a href="http://bugs.mysql.com/bug.php?id=38078" rel="nofollow">http://bugs.mysql.com/bug.php?id=38078</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Toby</title>
		<link>http://www.mysqlperformanceblog.com/2008/07/04/recovering-innodb-table-corruption/#comment-326969</link>
		<dc:creator>Toby</dc:creator>
		<pubDate>Sat, 12 Jul 2008 13:51:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=430#comment-326969</guid>
		<description>Did you file a bug on the CHECK TABLE deficiency?</description>
		<content:encoded><![CDATA[<p>Did you file a bug on the CHECK TABLE deficiency?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin Huff</title>
		<link>http://www.mysqlperformanceblog.com/2008/07/04/recovering-innodb-table-corruption/#comment-324561</link>
		<dc:creator>Justin Huff</dc:creator>
		<pubDate>Tue, 08 Jul 2008 02:53:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=430#comment-324561</guid>
		<description>The trick is to make sure you time the hardware work when it's REALLY hot in the office.  The data center is MUCH cooler:)</description>
		<content:encoded><![CDATA[<p>The trick is to make sure you time the hardware work when it&#8217;s REALLY hot in the office.  The data center is MUCH cooler:)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: peter</title>
		<link>http://www.mysqlperformanceblog.com/2008/07/04/recovering-innodb-table-corruption/#comment-324552</link>
		<dc:creator>peter</dc:creator>
		<pubDate>Tue, 08 Jul 2008 02:42:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=430#comment-324552</guid>
		<description>Oh well,

Then you can try more rounds replacing hardware :)</description>
		<content:encoded><![CDATA[<p>Oh well,</p>
<p>Then you can try more rounds replacing hardware <img src='http://www.mysqlperformanceblog.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin Huff</title>
		<link>http://www.mysqlperformanceblog.com/2008/07/04/recovering-innodb-table-corruption/#comment-324454</link>
		<dc:creator>Justin Huff</dc:creator>
		<pubDate>Mon, 07 Jul 2008 23:19:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=430#comment-324454</guid>
		<description>Peter,
Yeah, it's just a slave for reporting, so it's not a big deal when it acts up....</description>
		<content:encoded><![CDATA[<p>Peter,<br />
Yeah, it&#8217;s just a slave for reporting, so it&#8217;s not a big deal when it acts up&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: peter</title>
		<link>http://www.mysqlperformanceblog.com/2008/07/04/recovering-innodb-table-corruption/#comment-324450</link>
		<dc:creator>peter</dc:creator>
		<pubDate>Mon, 07 Jul 2008 23:16:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=430#comment-324450</guid>
		<description>Justin,

If it is just one box you may just better off moving stuff to other box - in many case simply calling box "buggy" and not using it for critical stuff is more cost effective than spending hundred of hours to figure out what exactly is the issue.

Also I should note if you have problem happening during the week in average  you can't be sure box is "good" by running just 24h worth of tests.</description>
		<content:encoded><![CDATA[<p>Justin,</p>
<p>If it is just one box you may just better off moving stuff to other box - in many case simply calling box &#8220;buggy&#8221; and not using it for critical stuff is more cost effective than spending hundred of hours to figure out what exactly is the issue.</p>
<p>Also I should note if you have problem happening during the week in average  you can&#8217;t be sure box is &#8220;good&#8221; by running just 24h worth of tests.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin Huff</title>
		<link>http://www.mysqlperformanceblog.com/2008/07/04/recovering-innodb-table-corruption/#comment-324384</link>
		<dc:creator>Justin Huff</dc:creator>
		<pubDate>Mon, 07 Jul 2008 21:56:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=430#comment-324384</guid>
		<description>Baron,
I did swap the card (a 3ware SATA controller), but there is a riser involved.  We have ~10 other systems with an identical setup, and this is the only one with issues.

Peter,
I suspected ram at first, so I ran memtest86 for 24hrs with no failures.  I think I have one ram permutation left to try before I swap the motherboard. 

Sadly, this problem takes over a week to appear in production, so it takes a while to narrow down:(

thanks!</description>
		<content:encoded><![CDATA[<p>Baron,<br />
I did swap the card (a 3ware SATA controller), but there is a riser involved.  We have ~10 other systems with an identical setup, and this is the only one with issues.</p>
<p>Peter,<br />
I suspected ram at first, so I ran memtest86 for 24hrs with no failures.  I think I have one ram permutation left to try before I swap the motherboard. </p>
<p>Sadly, this problem takes over a week to appear in production, so it takes a while to narrow down:(</p>
<p>thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: peter</title>
		<link>http://www.mysqlperformanceblog.com/2008/07/04/recovering-innodb-table-corruption/#comment-324248</link>
		<dc:creator>peter</dc:creator>
		<pubDate>Mon, 07 Jul 2008 16:34:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=430#comment-324248</guid>
		<description>Justin,

The memory subsystem (which included mainboard) also can be the problem.
In many cases with random Innodb corruptions  doing memory diagnostic with memtest86 or similar tools pointed the problems.</description>
		<content:encoded><![CDATA[<p>Justin,</p>
<p>The memory subsystem (which included mainboard) also can be the problem.<br />
In many cases with random Innodb corruptions  doing memory diagnostic with memtest86 or similar tools pointed the problems.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Baron Schwartz</title>
		<link>http://www.mysqlperformanceblog.com/2008/07/04/recovering-innodb-table-corruption/#comment-324234</link>
		<dc:creator>Baron Schwartz</dc:creator>
		<pubDate>Mon, 07 Jul 2008 15:46:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=430#comment-324234</guid>
		<description>How about your RAID controller?

Search Google for what Jeremy Cole has to say about LSI cards and risers -- there might be something relevant there.  Just a vague memory.</description>
		<content:encoded><![CDATA[<p>How about your RAID controller?</p>
<p>Search Google for what Jeremy Cole has to say about LSI cards and risers &#8212; there might be something relevant there.  Just a vague memory.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin Huff</title>
		<link>http://www.mysqlperformanceblog.com/2008/07/04/recovering-innodb-table-corruption/#comment-324230</link>
		<dc:creator>Justin Huff</dc:creator>
		<pubDate>Mon, 07 Jul 2008 15:41:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=430#comment-324230</guid>
		<description>Funny, we've had a DB box acting up (InnoDB complaining about page corruption) for several months. It's never the same page. The files on disk appear to be OK, it's like they get corrupted in memory. 

I've dumped/reloaded the DBs, and swapped nearly everything in the box. The last remaining pieces are the motherboard and the processors.

Yuck:(</description>
		<content:encoded><![CDATA[<p>Funny, we&#8217;ve had a DB box acting up (InnoDB complaining about page corruption) for several months. It&#8217;s never the same page. The files on disk appear to be OK, it&#8217;s like they get corrupted in memory. </p>
<p>I&#8217;ve dumped/reloaded the DBs, and swapped nearly everything in the box. The last remaining pieces are the motherboard and the processors.</p>
<p>Yuck:(</p>
]]></content:encoded>
	</item>
</channel>
</rss>
