I have an innodb table with about 21GB of data in it. Fairly reliably, even simple access of the table causes a crash. For example,
SELECT * FROM mirth.d_mc1 limit 1;
causes the server to crash. This is in the log.
Timestamp, Thread, Type, Details
, , , 2014-04-07 11:28:06 1cb8 InnoDB: File name .\mirth\d_mc1.ibd
, , , 2014-04-07 11:28:06 1cb8 InnoDB: File operation call: 'Windows aio' returned OS error 221.
, , , 2014-04-07 11:28:06 1cb8 InnoDB: Cannot continue operation.
After restart, it seems to be able to recover from binary log. According to the microsoft website, Error 221 is
ERROR_CHECKOUT_REQUIRED
221 (0xDD)
The file must be checked out before saving changes.
How to repeat:
I really have no idea how to repeat this bug. Whenever this particular table gets too big, I get this error.
SELECT * FROM mirth.d_mc1 limit 1;
causes the server to crash. This is in the log.
Timestamp, Thread, Type, Details
, , , 2014-04-07 11:28:06 1cb8 InnoDB: File name .\mirth\d_mc1.ibd
, , , 2014-04-07 11:28:06 1cb8 InnoDB: File operation call: 'Windows aio' returned OS error 221.
, , , 2014-04-07 11:28:06 1cb8 InnoDB: Cannot continue operation.
After restart, it seems to be able to recover from binary log. According to the microsoft website, Error 221 is
ERROR_CHECKOUT_REQUIRED
221 (0xDD)
The file must be checked out before saving changes.
How to repeat:
I really have no idea how to repeat this bug. Whenever this particular table gets too big, I get this error.