Bug #82847 mysqld crashes
Submitted: 2 Sep 2016 14:07 Modified: 16 Sep 2016 5:29
Reporter: Tim Smith Email Updates:
Status: Open Impact on me:
None 
Category:MySQL Server: DDL Severity:S1 (Critical)
Version:5.6.30 OS:Microsoft Windows (2012 R2 x64)
Assigned to: CPU Architecture:Any

[2 Sep 2016 14:07] Tim Smith
Description:
Mysqld crashes soon after doing recovery.

How to repeat:
1. Create two indexes in a single DML command on a single table. (use online DDL mode)
2. During the merge sort phase, force restart the server.
3. Windows performs chkdsk automatically.
4. After chkdsk finishes, Windows reboot itself again.
5. Start mysqld again. It performs recovery successfully.
6. After several minutes, mysqld crashes. 

2016-08-25 04:08:13 106c  InnoDB: Assertion failure in thread 4204 in file fsp0fsp.cc line 1867
InnoDB: Failing assertion: inode
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
[15 Sep 2016 14:45] Miguel Solorzano
Thank you for the bug report. Could you please provide (private if you wish) the create table statement, the number of rows and the create index statement. Thanks.