文档章节

mysql 无法启动

qii
 qii
发布于 2016/07/01 10:12
字数 488
阅读 73
收藏 0

错误信息

2016-07-01  9:37:56 2664 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2016-07-01  9:37:56 2664 [Note] InnoDB: The InnoDB memory heap is disabled
2016-07-01  9:37:56 2664 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2016-07-01  9:37:56 2664 [Note] InnoDB: Memory barrier is not used
2016-07-01  9:37:56 2664 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-07-01  9:37:57 2664 [Note] InnoDB: Not using CPU crc32 instructions
2016-07-01  9:37:57 2664 [Note] InnoDB: Initializing buffer pool, size = 64.0M
2016-07-01  9:37:57 2664 [Note] InnoDB: Completed initialization of buffer pool
2016-07-01  9:37:57 2664 [Note] InnoDB: Highest supported file format is Barracuda.
2016-07-01  9:37:57 2664 [Note] InnoDB: The log sequence numbers 37077739 and 37077739 in ibdata files do not match the log sequence number 37077749 in the ib_logfiles!
2016-07-01  9:37:57 2664 [Note] InnoDB: Database was not shutdown normally!
2016-07-01  9:37:57 2664 [Note] InnoDB: Starting crash recovery.
2016-07-01  9:37:57 2664 [Note] InnoDB: Reading tablespace information from the .ibd files...
2016-07-01  9:38:11 2664 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace tp5/qii_menu uses space ID: 21 at filepath: .\tp5\qii_menu.ibd. Cannot open tablespace ymtx/az_brand which uses space ID: 21 at filepath: .\ymtx\az_brand.ibd
InnoDB: Error: could not open single-table tablespace file .\ymtx\az_brand.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.

看最后一句,在my.ini里面设置innodb_force_recovery>0试试

innodb_force_recovery=1

重启mysql,搞定了。

 

but,问题又来了。

insert数据,没有问题。但是update,就不行了。

1036:table xx is read only.

打开日志一看。

innodb Started in read only mode

wtf.

翻到一篇帖子:

http://stackoverflow.com/questions/25394466/my-sql-error-1015-cant-lock-file-errno-165-table-is-read-only-innodb-en

把刚才加的那句配置,删掉,重启,ok。

© 著作权归作者所有

共有 人打赏支持
qii

qii

粉丝 13
博文 77
码字总数 23520
作品 0
昆明
高级程序员

暂无文章

使用Newtonsoft将DataTable转Json

使用Newtonsoft将DataTable转Json Newtonsoft提供的将DataTable转成Json: /// <summary> /// DataTable转Json /// </summary> /// <param name="dt"></param> /// <ret......

DemonsI
5分钟前
0
0
centos7安装zookeeper3.4.6

注:zookeeper充当注册中心 下载地址 http://mirror.bit.edu.cn/apache/zookeeper/zookeeper-3.4.6/ 单机 下载完成后,将安装包上传值服务器,解压 tar xvzf zookeeper-3.4.6.tar.gz 进入解...

码代码的小司机
6分钟前
0
0
136. Single Number

136. Single Number 题意:一个数组中所有数字都是两两相同,只有一个数字是单独的,求出这个数字的值。 很简单的题,使用异或就能处理。 异或介绍:bit位上的值不同,异或后,值为1.否则为0...

117
8分钟前
0
0
Hash和HashCode深入理解

目录介绍 1.Hash的作用介绍 1.1 Hash的定义 1.2 Hash函数特性 1.3 Hash的使用场景 2.如何判断两个对象相等 2.1 判断两个字符串 2.2 判断两个int数值 2.3 其他基本类型 3.HashCode深入分析 3....

潇湘剑雨
14分钟前
0
0
ecshop 漏洞如何修复 补丁升级与安全修复详情

目前ecshop漏洞大面积爆发,包括最新版的ecshop 3.0,ecshop 4.0,ecshop2.7.3全系列版本都存在着高危网站漏洞,导致网站被黑,被篡改,被挂马,许多商城系统深受其漏洞的攻击,给商城的运营者...

网站安全
14分钟前
0
0

没有更多内容

加载失败,请刷新页面

加载更多

返回顶部
顶部