Mysql Got error 127 when reading table

Mysql 数据库errlog中有错误日志,提示:Got error 127 when reading table xxx!Mysql 版本:『mysql Ver 14.14 Distrib 5.6.35, for Linux (x86_64) using EditLine wrapper』,下面是具体的解决办法:

错误日志:
2017-02-03 14:48:39 27759 [ERROR] Got error 127 when reading table ‘./sudops_com/sudops_options’
2017-02-03 14:48:41 27759 [ERROR] Got error 127 when reading table ‘./sudops_com/sudops_options’
2017-02-03 14:49:33 27759 [ERROR] Got error 127 when reading table ‘./sudops_com/sudops_options’

修复办法:

mysql> use sudops_com      
mysql> check table sudops_options;
+--------------------------------+-------+----------+----------------------------------------------------------+
| Table                          | Op    | Msg_type | Msg_text                                                 |
+--------------------------------+-------+----------+----------------------------------------------------------+
| sudops_com.sudops_options      | check | warning  | Table is marked as crashed                               |
| sudops_com.sudops_options      | check | warning  | 2 clients are using or haven't closed the table properly |
| sudops_com.sudops_options      | check | warning  | Size of datafile is: 2488268       Should be: 2488132    |
| sudops_com.sudops_options      | check | error    | Wrong record length 1374362 of 1374495 at 9956           |
| sudops_com.sudops_options      | check | error    | Corrupt                                                  |
+--------------------------------+-------+----------+----------------------------------------------------------+
5 rows in set (0.32 sec)


mysql> repair table sudops_options;
+--------------------------------+--------+----------+------------------------------------------------------+
| Table                          | Op     | Msg_type | Msg_text                                             |
+--------------------------------+--------+----------+------------------------------------------------------+
| sudops_com.sudops_options      | repair | info     | Wrong block with wrong total length starting at 9956 |
| sudops_com.sudops_options      | repair | warning  | Number of rows changed from 351 to 350               |
| sudops_com.sudops_options      | repair | status   | OK                                                   |
+--------------------------------+--------+----------+------------------------------------------------------+
3 rows in set (0.19 sec)

repair之后再次check下表状态:

mysql> check table sudops_options;
+--------------------------------+-------+----------+----------+
| Table                          | Op    | Msg_type | Msg_text |
+--------------------------------+-------+----------+----------+
| sudops_com.sudops_options      | check | status   | OK       |
+--------------------------------+-------+----------+----------+
1 row in set (0.03 sec)

可以看到已经OK了 :)

再次看下mysql的 errlog:
2017-02-03 14:51:05 27759 [ERROR] /usr/sbin/mysqld: Table ‘./sudops_com/sudops_options’ is marked as crashed and should be repaired
2017-02-03 14:51:05 27759 [ERROR] /usr/sbin/mysqld: Table ‘./sudops_com/sudops_options’ is marked as crashed and should be repaired
2017-02-03 14:51:05 27759 [ERROR] /usr/sbin/mysqld: Table ‘./sudops_com/sudops_options’ is marked as crashed and should be repaired
2017-02-03 14:51:15 27759 [Note] Found 350 of 351 rows when repairing ‘./sudops_com/sudops_options

mysql表已经修复成功!

u2

Related Posts

mysql连接失败:The driver has not received any packets from the server

解决java spring连接mysql报错问题,增加连接串参数

Read more

python cx-Oracle 驱动安装

安装oracle驱动 cx-Oracle驱动二进制版本下载地…

Read more

You Missed

Anthropic 指控阿里蒸馏攻击:AI 军备竞赛的拐点

  • u2
  • 6月 25, 2026
  • 70 views

当AI开始吃自己:数据污染正在成为大模型行业最隐秘的危机

  • u2
  • 6月 25, 2026
  • 86 views

Google 用 AI「杀死」Google

  • u2
  • 6月 22, 2026
  • 94 views

封禁Fable 5:当美国政府成为AI的”守门人”

  • u2
  • 6月 21, 2026
  • 170 views

27亿美元没留住的人,奥特曼等了十年

  • u2
  • 6月 19, 2026
  • 84 views

OpenAI Codex 发布角色插件:当AI开始理解「分析师」和「销售」是两种不同的物种

  • u2
  • 6月 15, 2026
  • 139 views
OpenAI Codex 发布角色插件:当AI开始理解「分析师」和「销售」是两种不同的物种