MySQL Forums
Forum List  »  Install & Repo

Mysql crash with OS error 1217
Posted by: deepak m
Date: July 30, 2013 11:11PM

We had MySQL server version 5.1.43 installed on a Windows Server machine which we recently upgraded to version 5.6.10. After the upgrade the MySQL server has been crashing quite frequently.
I'm developer on the project the project and we don't have a DBA at hand. Any help is much appreciated.
Below is the log

Quote

Version: '5.6.10' socket: '' port: 3306 MySQL Community Server (GPL)
2013-07-26 19:23:07 ee4 InnoDB: Operating system error number 1117 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
2013-07-26 19:23:07 ee4 InnoDB: File name .\db_schema\mail_user_1366132026070.ibd
2013-07-26 19:23:07 ee4 InnoDB: File operation call: 'Windows aio' returned OS error 1217.
2013-07-26 19:23:07 ee4 InnoDB: Cannot continue operation.
2013-07-26 19:23:07 1244 InnoDB: Operating system error number 1117 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
2013-07-26 19:23:07 1244 InnoDB: File name .\db_schema\mail_metadata_1366132026070.ibd
2013-07-26 19:23:07 1244 InnoDB: File operation call: 'Windows aio' returned OS error 1217.
2013-07-26 19:23:07 1244 InnoDB: Cannot continue operation.
2013-07-29 09:25:25 808 [Note] Plugin 'FEDERATED' is disabled.
2013-07-29 09:25:25 808 [Note] InnoDB: The InnoDB memory heap is disabled
2013-07-29 09:25:25 808 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-07-29 09:25:25 808 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-07-29 09:25:25 808 [Note] InnoDB: CPU does not support crc32 instructions
2013-07-29 09:25:25 808 [Note] InnoDB: Initializing buffer pool, size = 1.5G
2013-07-29 09:25:25 808 [Note] InnoDB: Completed initialization of buffer pool
2013-07-29 09:25:25 808 [Note] InnoDB: Highest supported file format is Barracuda.
2013-07-29 09:25:25 808 [Note] InnoDB: The log sequence numbers 109588702362 and 109588702362 in ibdata files do not match the log sequence number 109677270283 in the ib_logfiles!
2013-07-29 09:25:25 808 [Note] InnoDB: Database was not shutdown normally!
2013-07-29 09:25:25 808 [Note] InnoDB: Starting crash recovery.
2013-07-29 09:25:25 808 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-07-29 09:25:26 808 [Note] InnoDB: Restoring possible half-written data pages
2013-07-29 09:25:26 808 [Note] InnoDB: from the doublewrite buffer...
2013-07-29 09:25:26 808 [Note] InnoDB: 128 rollback segment(s) are active.
2013-07-29 09:25:26 808 [Note] InnoDB: Waiting for purge to start
2013-07-29 09:25:26 808 [Note] InnoDB: 1.2.10 started; log sequence number 109677270283
2013-07-29 09:25:26 808 [Note] Server hostname (bind-address): '*'; port: 3306
2013-07-29 09:25:26 808 [Note] IPv6 is available.
2013-07-29 09:25:26 808 [Note] - '::' resolves to '::';
2013-07-29 09:25:26 808 [Note] Server socket created on IP: '::'.
2013-07-29 09:25:27 808 [Note] Event Scheduler: Loaded 0 events
2013-07-29 09:25:27 808 [Note] mysqld.exe: ready for connections.
Version: '5.6.10' socket: '' port: 3306 MySQL Community Server (GPL)
2013-07-29 17:13:46 c4c InnoDB: Operating system error number 1117 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
2013-07-29 17:13:46 c4c InnoDB: File name .\db_schema\mail_metadata_1366132026070.ibd
2013-07-29 17:13:46 c4c InnoDB: File operation call: 'Windows aio' returned OS error 1217.
2013-07-29 17:13:46 c4c InnoDB: Cannot continue operation.
2013-07-29 17:13:46 dec InnoDB: Operating system error number 1117 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
2013-07-29 17:13:47 dec InnoDB: File name .\db_schema\mail_user_1366132026070.ibd
2013-07-29 17:13:47 dec InnoDB: File operation call: 'Windows aio' returned OS error 1217.
2013-07-29 17:13:47 dec InnoDB: Cannot continue operation.
I have modified the log to remove the database name.

MySQL is running with the default configurations. Below are the additional parameters we have set:
--max_allowed_packet=1024M
--default-storage-engine=InnoDB
--port=3306
--innodb_buffer_pool_size=1536M
--transaction-isolation=READ-COMMITTED

Thank you

Options: ReplyQuote


Subject
Written By
Posted
Mysql crash with OS error 1217
July 30, 2013 11:11PM


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.