本文目录一览：
- 1、mysql怎么解决提示Got error 28 from storage engine问题
- 2、mysql怎么解决提示Got error 28 from storage engine的问题？
- 3、访问MYSQL 偶尔会出现以下报错信息 1030 - Got error 12 from storage engine 是什么原因，怎么解决？
- 4、mysql 错误 以下是错误日志的内容 我使用fleaphp 弄的网站 fleaphp 提示的错误是 SQL 错误消息: "Got err
- 5、mysql federated经常报错：Got an error writing communication packets
mysql怎么解决提示Got error 28 from storage engine问题
数据库用的临时目录空间不够。
解决办法：
清空/tmp目录，或者修改my.cnf中的tmpdir参数，指向具有足够空间目录
mysql怎么解决提示Got error 28 from storage engine的问题？
解决方案：
1、在数据库所在的linux服务器上，用df查看磁盘使用情况。
注：df是基于文件系统总体来计算，通过文件系统中未分配空间来确定系统中已经分配空间的大小。df命令可以获取硬盘占用了多少空间，还剩下多少空间，它也可以显示所有文件系统对i节点和磁盘块的使用情况。
2、在数据库所在的linux服务器上，用du查看目录大小。
注：du的英文为:disk usage,含义是磁盘空间使用情况，功能是逐级进入指定目录的每一个子目录并显示该目录占用文件系统数据块的情况，如果没有指定目录，则对当前的目录进行统计。
3、删除相应的大文件，或者表数据。
访问MYSQL 偶尔会出现以下报错信息 1030 - Got error 12 from storage engine 是什么原因，怎么解决？
你应该是使用的innodb，检查你的my.cnf或my.ini，里面会有一个参数innodb_force_recovery,你看看他的值，默认是没有这个参数，没有的话，他的默认值是0，这个参数的值如果大于0，innodb会被禁止使用insert、update、delete命令，你可以尝试将他的值设置为0，看看你的mysql是否正常，如果正常就用就行了。
mysql 错误 以下是错误日志的内容 我使用fleaphp 弄的网站 fleaphp 提示的错误是 SQL 错误消息: "Got err
"Column count of mysql.event is wrong"，你的mysql.event表坏了，在bin目录下运行mysql_upgrade.exe执行下修复。
下面提示存储引擎错误，估计是你的表由于计算机异常重启导致物理损坏了。
用check table xxxx检查下表吧。
mysql federated经常报错：Got an error writing communication packets
可以建立一个Events定时对Federated的表进行flush。具体可以见
Related to Federated Table :
Whenever a query is issued against a federated table, a single/multiple [ depends on Number = table_open_cache_instances] connection will be created from the DB instance hosting the federated table to the DB instance hosting the main table. If those single/mutiple connection on the DB instance hosting main table expires because of [wait_timeout,connect_timeout] or if those gets terminated manually , any new queries on federated table will result in "ERROR 1158 (08S01) at line 1: Got an error reading communication packets" on the DB instance hosting the federated table.
Reason : Flushing of the federated table does not happen properly from the table_open_cache_instances ,
Solution : To avoid this, the temporary solution is to manually/forcefully flush only those federated tables once before every [wait_timeout,connect_timeout] seconds. In our case we put the flush command in event_scheduler since the number of federated tables were very less and we knew exactly which federated tables were rarely getting queried with gap of more than [wait_timeout,connect_timeout] seconds. This used to affect even our MEB backup when it used execute "flush tables with READ lock".
flush table federated_table_name; -- executed every 4 hours
Key : The frequency with which it errors depends on how many table_open_cache_instances is configured on the Instance.
Since then, after putting the manual flush of federated tables with a frequence less than [wait_timeout,connect_timeout] , this issue has not showed up. Hope this helps.