MySQL无法启动-ibdata1损坏了吗? -操作系统错误编号13-权限问题 [英] Mysql won't start - ibdata1 corrupt? - operating system error number 13 - permissions issue

查看:428
本文介绍了MySQL无法启动-ibdata1损坏了吗? -操作系统错误编号13-权限问题的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

服务器因电源故障而关闭.
MySQL无法立即启动.
磁盘未满. Syslog在下面

Server shutdown from power failure.
Mysql will not start now.
Disk is not full. Syslog is below

Oct 11 15:03:31 joe mysqld_safe[24757]: started
Oct 11 15:03:31 joe mysqld[24760]: 101011 15:03:31  InnoDB: Operating system error number 13 in a file operation.
Oct 11 15:03:31 joe mysqld[24760]: InnoDB: The error means mysqld does not have the access rights to
Oct 11 15:03:31 joe mysqld[24760]: InnoDB: the directory.
Oct 11 15:03:31 joe mysqld[24760]: InnoDB: File name ./ibdata1
Oct 11 15:03:31 joe mysqld[24760]: InnoDB: File operation call: 'create'.
Oct 11 15:03:31 joe mysqld[24760]: InnoDB: Cannot continue operation.

推荐答案

文件未损坏.您可以使用"perror"找出这些错误的来源.即

The file is not corrupt. You can find out the source of these errors with 'perror'. i.e.

toaster:~ morgo$ perror 13
OS error code  13:  Permission denied

InnoDB具有损坏检测功能(页面校验和),会很高兴地告诉您是否是问题所在.

InnoDB has corruption detection (page checksums) and would happily tell you if that were the problem.

目录权限已更改,或者您的my.cnf文件已被清除,并且它正在尝试在其他位置重新创建数据文件.

Either the directory permissions have changed, or your my.cnf file has been hosed, and it's trying to recreate data files somewhere else.

这篇关于MySQL无法启动-ibdata1损坏了吗? -操作系统错误编号13-权限问题的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆