Mysql无法启动 使用GPT Drive

错误日志:
160328 11:23:28  InnoDB: Initializing buffer pool, size = 45.0M
160328 11:23:28  InnoDB: Completed initialization of buffer pool
160328 11:23:28  InnoDB: Operating system error number 87 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/operating-system-error-codes.html
InnoDB: File name .\ib_logfile0
InnoDB: File operation call: 'aio read'.
InnoDB: Cannot continue operation.

解决方法:
配置文件加入: innodb_flush_method=normal

参考来源:
http://bugs.mysql.com/bug.php?id=28913
差不多是这个样子的,The main reason to use GPT is that it allows for drives > 2TB.  Because of the drive's large size, the OS defaults to a larger block size than the default 4096 bytes.This in turn breaks MySQL, as by default it does direct writes to the drive w/o caching (as it has its own internal caching).Windows requires non-cached disk writes to be a multiple of the block size.

修改时间 2016-03-28

真诚赞赏,手留余香
赞赏
随机推荐
ES2020 "?." 和 "??" 可选链
白无常「两小时」
iconfont 字体生成原理
Node.js WebSocket
Windows 下 Redis 安装配置 PHP 模块
(转)关于百度地图和高德地图,关于地图坐标系
Git 对库文件权限的管理 git config core.filemode
安卓项目结构图
CentOS 磁盘空间相关命令
CentOS7 安装 LAMP 和 Mod Security 手记
QQ号

微信联系我

夜间模式切换
回到顶部