Group: Member Post Group: Newbie
Posts: 2
Status:  |
Hello,
I was using mySQL with no problems a couple of days ago but since restarting my machine, I can no longer launch my SQL.
This is the error log output:
2014-05-05 22:25:18 5612 [Note] InnoDB: Starting crash recovery.
2014-05-05 22:25:18 5612 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-05-05 22:25:18 5612 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace backup/slave_relay_log_info uses space ID: 3 at filepath: .\backup\slave_relay_log_info.ibd. Cannot open tablespace my_client/wp_terms which uses space ID: 3 at filepath: .\my_client\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\my_client\wp_terms.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
... I tried renaming wp_terms.ibd but that didn't work
I tried moving:
innodb_index_stats.frm
innodb_index_stats.ibd
innodb_table_stats.frm
innodb_table_stats.ibd
slave_master_info.ibd
slave_relay_log_info.frm
slave_relay_log_info.ibd
slave_worker_info.frm
slave_worker_info.ibd
... to a different folder, but that didn't work.
I've searched for my.cnf but can't find any such file - where should it be?
What else can I try to get mySQL back up..?
Thanks in advance
|
Powered By AEF 1.0.8 © 2007-2008 Electron Inc.
May 5, 2014, 9:48 pm
