Recently I had a case when a customer deleted the InnoDB main table space – ibdata1 – and redo logs – ib_logfile*. MySQL keeps InnoDB files open all the time. The following recovery technique is based on this fact and it allowed to salvage the database. Actually, the files were deleted long time ago – [...]
Announcing Percona Server 5.5.24-26.0
June 1, 2012 By 9 Comments
Percona is glad to announce the release of Percona Server 5.5.24-26.0 on June 1st, 2012 (Downloads are available here and from the Percona Software Repositories). Based on MySQL 5.5.24, including all the bug fixes in it, Percona Server 5.5.24-26.0 is now the current stable release in the 5.5 series. All of Percona‘s software is open-source and free, all the details of the release can [...]
Percona Server 5.5.21-25.1 released!
March 29, 2012 By 8 Comments
Percona is glad to announce the release of Percona Server 5.5.21-25.1 on March 30, 2012 (Downloads are available here and from the Percona Software Repositories). Based on MySQL 5.5.21, including all the bug fixes in it, Percona Server 5.5.21-25.1 is now the current stable release in the 5.5 series. All of Percona‘s software is open-source and free, all the details of the release can [...]
Verifying backup integrity with CHECK TABLES
February 1, 2012 By 4 Comments
An attendee to Espen’s recent webinar asked how to check tables for corruption. This kind of ties into my recent post on InnoDB’s handling of corrupted pages, because the best way to check for corruption is with CHECK TABLES, but if a page is corrupt, InnoDB will crash the server to prevent access to the [...]
How Percona Server handles data corruption more gracefully
January 6, 2012 By 2 Comments
I got a question a while ago about how Percona Server handles corrupted data more gracefully than the standard MySQL server from Oracle. The short version is that it won’t crash the whole server. With standard MySQL from Oracle, if any page of data in InnoDB is found to be corrupt, the entire instance will [...]
Bug#12704861
November 20, 2011 By 1 Comment
As Mark pointed out, there isn’t a lot of detail in the release notes about what could potentially be a very serious problem that is fixed in MySQL 5.1.60. I’ll repeat here the full documentation from the release notes: “InnoDB Storage Engine: Data from BLOB columns could be lost if the server crashed at a precise [...]
Make your file system error resilient
August 24, 2011 By 8 Comments
One of the typical problems I see setting up ext2/3/4 file system is sticking to defaults when it comes to behavior on errors. By default these filesystems are configured to Continue when error (such as IO error or meta data inconsistency) is discovered which can continue spreading corruption. This manifests itself in a worst way [...]
Connecting orphaned .ibd files
May 13, 2011 By 19 Comments
There are two ways InnoDB can organize tablespaces. First is when all data, indexes and system buffers are stored in a single tablespace. This is typicaly one or several ibdata files. A well known innodb_file_per_table option brings the second one. Tables and system areas are split into different files. Usually system tablespace is located in [...]
Percona Server 5.5.10 (Release Candidate)
April 4, 2011 By 4 Comments
Percona Server release 5.5.10-20.1 is now available for download. This is a release candidate for the Percona Server 5.5 series. In addition to MySQL 5.5.10 now being the base version, here are the changes that have been made since Percona Server beta release 5.5.8-20.0:
Battery Learning still problem many years after
February 10, 2011 By 7 Comments
The performance problems caused by battery auto learning go many years back. We wrote about it, other people from MySQL Community too. The situation did not get better, at least not with Dell RAID controllers, H700 and H800 have the same problem too. At the same time situation got worse as a lot more people [...]
