MySQL Forums
Forum List  »  InnoDB

Recover from a broken ibdata1
Posted by: Jeff boston
Date: December 08, 2017 01:51AM

Hello all,

I was trying to import an old .sql into existing database. But my mysql service suddenly stopped. After that I'm not able to. restart the server. I don't have any other thread using this file. I've tried add innodb_force_recovery = 6 in my.cnf. But it doesn't help. It seems that my ibdata1 is broken. Is there any way I can resume it? Can anyone help? Thanks in advance !!!

==================
2017-04-03T20:22:49.753346Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-04-03T20:22:50.754366Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2017-04-03T20:22:50.754397Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-04-03T20:22:51.755926Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2017-04-03T20:22:51.755950Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-04-03T20:22:52.760218Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2017-04-03T20:22:52.760248Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-04-03T20:22:53.761599Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2017-04-03T20:22:53.761623Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-04-03T20:22:54.766279Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 35
2017-04-03T20:22:54.766308Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-04-03T20:22:54.766316Z 0 [Note] InnoDB: Unable to open the first data file
2017-04-03T20:22:54.766342Z 0 [ERROR] InnoDB: Operating system error number 35 in a file operation.
2017-04-03T20:22:54.766369Z 0 [ERROR] InnoDB: Error number 35 means 'Resource temporarily unavailable'
2017-04-03T20:22:54.766376Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2017-04-03T20:22:54.766382Z 0 [ERROR] InnoDB: Cannot open datafile './ibdata1'
2017-04-03T20:22:54.766406Z 0 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!
2017-04-03T20:22:54.766417Z 0 [ERROR] InnoDB: Plugin initialization aborted with error Cannot open a file
2017-04-03T20:22:55.072312Z 0 [ERROR] Plugin 'InnoDB' init function returned error.
2017-04-03T20:22:55.072337Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-04-03T20:22:55.072355Z 0 [ERROR] Failed to initialize plugins.
2017-04-03T20:22:55.072361Z 0 [ERROR] Aborting

2017-04-03T20:22:55.072372Z 0 [Note] Binlog end
2017-04-03T20:22:55.072484Z 0 [Note] Shutting down plugin 'CSV'
2017-04-03T20:22:55.072678Z 0 [Note] /usr/local/mysql/bin/mysqld: Shutdown complete

Options: ReplyQuote


Subject
Views
Written By
Posted
Recover from a broken ibdata1
214
December 08, 2017 01:51AM
88
January 04, 2018 01:00AM


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.