日志:
120725 08:02:48 mysqld started
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
120725 8:02:48 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
120725 8:02:48 InnoDB: Operating system error number 13 in a file operation.
InnoDB: The error means mysqld does not have the access rights to
InnoDB: the directory.
InnoDB: Error: could not open single-table tablespace file
InnoDB: ./geilitest2.bak/news_content.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.
120725 08:02:48 mysqld ended
启动mysql: Timeout error occurred trying to start MySQL Daemon
答案:2 悬赏:10
解决时间 2021-03-22 18:48
- 提问者网友:逝爱
- 2021-03-22 09:09
最佳答案
- 二级知识专家网友:不羁的心
- 2021-03-22 10:20
直接把geilitest2.bak目录下的所有后缀为.ibd的文件删除就好了
全部回答
- 1楼网友:丢不掉的轻狂
- 2021-03-22 11:20
解决办法执行这个命令:# /usr/bin/mysql_install_db
我要举报
如以上问答内容为低俗、色情、不良、暴力、侵权、涉及违法等信息,可以点下面链接进行举报!
大家都在看
推荐资讯