Kristian Nielsen added a comment - 2014-11-25 15:22 Seen two times in 10.0 trees also: http://buildbot.askmonty.org/buildbot/reports/cross_reference#branch=&revision=&platform=&dt=&bbnum=&typ=&info=&fail_name=rpl.rpl_gtid_crash&fail_variant=&fail_info_short=&fail_info_full=database+page+corruption+or+a+failed&limit=100 The warning in the error log looks like this: 141123 12:47:54 [Note] InnoDB: Restoring possible half-written data pages 141123 12:47:54 [Note] InnoDB: from the doublewrite buffer... InnoDB: Warning: database page corruption or a failed InnoDB: file read of space 6 page 3. InnoDB: Trying to recover it from the doublewrite buffer. 141123 12:47:54 [Note] InnoDB: Recovered the page from the doublewrite buffer. So there is a half-written page, but it is recovered correctly from the double-write buffer. Since we deliberately crash the server in the test case, half-written pages is not unexpected. So I added a suppression for this warning in the test case.

Kristian Nielsen added a comment - 2015-01-22 16:40 Same issue applies to innodb.group_commmit_crash and innodb.group_commit_crash_no_optimize_thread