<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Innochecksum on FromDual GmbH</title><link>https://www.fromdual.com/tags/innochecksum/</link><description>Recent content in Innochecksum on FromDual GmbH</description><generator>Hugo</generator><language>en-GB</language><managingEditor>oli.sennhauser@fromdual.com (Oli Sennhauser)</managingEditor><webMaster>oli.sennhauser@fromdual.com (Oli Sennhauser)</webMaster><copyright>© FromDual GmbH</copyright><lastBuildDate>Wed, 05 Aug 2020 17:21:13 +0000</lastBuildDate><atom:link href="https://www.fromdual.com/tags/innochecksum/index.xml" rel="self" type="application/rss+xml"/><item><title>Shrinking InnoDB system tablespace file ibdata1 PoC</title><link>https://www.fromdual.com/blog/shrinking-innodb-system-tablespace-file-ibdata1-poc/</link><pubDate>Sat, 08 Dec 2012 13:43:11 +0000</pubDate><author>oli.sennhauser@fromdual.com (Oli Sennhauser)</author><guid>https://www.fromdual.com/blog/shrinking-innodb-system-tablespace-file-ibdata1-poc/</guid><description>&lt;p&gt;In this weeks MySQL workshop we were discussing, beside other things, about the &lt;code&gt;innodb_file_per_table&lt;/code&gt; parameter and its advantages of enabling it. In addition there was a discussion if the InnoDB system tablespace file can be shrinked once it has been grown very large or not. We all know the answer: &lt;em&gt;The InnoDB system tablespace file does never shrink again.&lt;/em&gt;&lt;/p&gt;</description></item><item><title>Which table is hit by an InnoDB page corruption?</title><link>https://www.fromdual.com/blog/innodb-table-hit-by-page-corruption/</link><pubDate>Mon, 02 Aug 2010 17:49:38 +0000</pubDate><author>oli.sennhauser@fromdual.com (Oli Sennhauser)</author><guid>https://www.fromdual.com/blog/innodb-table-hit-by-page-corruption/</guid><description>&lt;p&gt;InnoDB is known to have crash-recovery capabilities and thus is called a crash safe storage engine (in contrary to MyISAM). Nevertheless under certain circumstances it seems like InnoDB pages can get corrupt during a crash and then a manual crash-recovery is needed.&lt;/p&gt;</description></item><item><title>Can you trust your MySQL backup?</title><link>https://www.fromdual.com/blog/can-you-trust-your-backup/</link><pubDate>Thu, 11 Feb 2010 22:06:00 +0000</pubDate><author>oli.sennhauser@fromdual.com (Oli Sennhauser)</author><guid>https://www.fromdual.com/blog/can-you-trust-your-backup/</guid><description>&lt;p&gt;Today a customer with corrupted data files showed up. When we enquired a bit more he told us that he had a broken I/O controller. This is one of the worst things which can happen to you!&lt;/p&gt;</description></item><item><title>What is CHECK TABLE doing with InnoDB tables?</title><link>https://www.fromdual.com/blog/what-is-check-table-doing-with-innodb/</link><pubDate>Fri, 29 Jan 2010 21:37:00 +0000</pubDate><author>oli.sennhauser@fromdual.com (Oli Sennhauser)</author><guid>https://www.fromdual.com/blog/what-is-check-table-doing-with-innodb/</guid><description>&lt;p&gt;Recently we had a case where a customer got some corrupted blocks in his InnoDB tables. His largest tables where quite big, about 30 to 100 Gbyte. Why he got this corrupted blocks we did not find out yet (disk broken?).&lt;/p&gt;</description></item></channel></rss>