请帮我分析分析下这错误日志，以及提供个好的办法

icer_repls

rushm 发表于 2012-3-20 16:10
非常感谢斑竹的分析。
这台机昨天出问题才接手的。是共享表空间。ibdata1目前350G。还好数据要求不是很苛 ...

我看了一下 最开始是由这个引起的Trx read view will not see trx with id >= 178FECCA1, sees < 178FE97BE

感觉是undo段出了问题。

jinguanding

rushm 发表于 2012-3-20 16:10
非常感谢斑竹的分析。
这台机昨天出问题才接手的。是共享表空间。ibdata1目前350G。还好数据要求不是很苛 ...

后续改成单表空间吧！

这样管理起来方便，性能也会更好些，主要是担心碎片的问题！

error 日志我看看

jinguanding

120319 10:53:56 [Warning] IP address '192.168.0.47' could not be resolved: Name or service not known
120319 10:53:56 [Warning] IP address '192.168.0.162' could not be resolved: Name or service not known
120319 10:53:56 [Warning] IP address '192.168.0.47' could not be resolved: Name or service not known
120319 10:53:57 [Warning] IP address '192.168.0.162' could not be resolved: Name or service not known
120319 10:53:58 [Warning] IP address '192.168.0.162' could not be resolved: Name or service not known
120319 10:53:58 [Warning] IP address '192.168.0.47' could not be resolved: Name or service not known
120319 10:53:59 [Warning] IP address '192.168.0.47' could not be resolved: Name or service not known
120319 10:53:59 [Warning] IP address '192.168.0.47' could not be resolved: Name or service not known
InnoDB: Error: tried to read 16384 bytes at offset 0 3526639616.
InnoDB: Was only able to read 12288.
120319 11:04:00  InnoDB: Operating system error number 0 in a file operation.


很奇怪的事情，为何报这些IP无法进行解析之后再就是报读的错误，是不是设置啥？ 或者 使用共享存储啥的？？？
是不是禁用了啥？my.cnf文件贴出来.....

rushm

jinguanding 发表于 2012-3-21 14:19
120319 10:53:56 [Warning] IP address '192.168.0.47' could not be resolved: Name or service not known ...

这个我知道，是他之前没禁用DNS反向解析，加入skip-name-resolve参数这种信息就不会有了。