MySQL Forums
Forum List  »  InnoDB

Re: Power failure and innodb
Posted by: Marko Mäkelä
Date: February 03, 2015 05:09AM

Hi Smita,
(You were the one who contacted me by email, causing me to do some research and file Bug#75697.)

Like with any form of corruption, you should start from the scratch and restore the system from backups. If you do not have recent backups, you could basically run mysqldump, but use the READ UNCOMMITTED isolation level, and cross your fingers that the contents of the database is consistent enough.

If you are willing to take the risk, you can cut some corners by patching the transaction ID field in the TRX_SYS page to a large enough value, so that no row in any index page can be in the future. A programmer should be able to figure out the details from my bug report.

Unfortunately, I do not know the root cause of this corruption (of the maximum transaction ID).

InnoDB should 'just work' and be fully crash-safe, even against power failures. (It is unsafe to disable the doublewrite buffer unless atomic writes are supported). There have been reports of trouble after a power failure, but it turned out that the fsync() system call was misbehaving.

Given that this issue seems to be rare (I only know about these two occurrences), I would suspect a hardware fault, such as a bit flipping spontaneously in the main memory. It would be good to run Memtest86 or Memtest86+ on the server. Corruption of the disk files should be usually caught by the page
checksums computed by InnoDB.

Options: ReplyQuote


Subject
Views
Written By
Posted
8138
January 27, 2014 09:45AM
2718
January 28, 2014 08:42AM
2761
February 24, 2014 06:21AM
2216
March 05, 2014 08:15AM
2072
March 05, 2014 10:42PM
1937
March 07, 2014 07:46AM
1439
February 02, 2015 09:33AM
1413
February 02, 2015 11:43AM
Re: Power failure and innodb
1520
February 03, 2015 05:09AM
1472
February 03, 2015 07:04PM
1890
February 04, 2015 01:03PM
1160
June 04, 2015 07:35AM
2591
March 31, 2014 06:16AM
1455
March 18, 2015 11:12AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.