查看:6605|回复：5
各位，紧急求助，刚刚监控到Mysql服务宕了，由于本人对Mysql还不是很熟悉，请大家协助，错误日志如下：
:05:23&&InnoDB: Error: Write to file /Databases/mysql/ibdata1 failed at offset 0 .
InnoDB: 16384 bytes should have been written, only -1 were written.
InnoDB: Operating system error number 5.
InnoDB: Check that your OS and file system support files of this size.
InnoDB: Check also that the disk is not full or a disk quota exceeded.
InnoDB: Error number 5 means 'Input/output error'.
InnoDB: Some operating system error numbers are described at
:05:24&&InnoDB: Assertion failure in thread
in file os/os0file.c line 4205
InnoDB: Failing assertion: ret
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: about forcing recovery.
08:05:24 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.
key_buffer_size=
read_buffer_size=2097152
max_used_connections=3
max_threads=100
thread_count=1
connection_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1057802 K&&bytes of memory
Hope that' if not, decrease some variables in the equation.
Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x85a71e]
/usr/sbin/mysqld(handle_fatal_signal+0x380)[0x6af410]
/lib64/libpthread.so.0[0x3b3340eb10]
/lib64/libc.so.6(gsignal+0x35)[0x3b]
/lib64/libc.so.6(abort+0x110)[0x3b32831d10]
/usr/sbin/mysqld(os_aio_simulated_handle+0x7c0)[0x7a7b20]
/usr/sbin/mysqld(fil_aio_wait+0x41)[0x773841]
/usr/sbin/mysqld[0x7d743c]
/lib64/libpthread.so.0[0x3b3340673d]
/lib64/libc.so.6(clone+0x6d)[0x3b328d3d1d]
The manual page at
information that should help you find out what is causing the crash.
:05:25 mysqld_safe Number of processes running now: 0
:05:26 mysqld_safe mysqld restarted
:05:26 [Warning] --myisam_max_extra_sort_file_size is deprecated and does nothing in this version.&&It will be removed in a future release.
:05:26 [Note] Plugin 'FEDERATED' is disabled.
:05:27&&InnoDB: Initializing buffer pool, size = 5.0G
:05:27&&InnoDB: Completed initialization of buffer pool
InnoDB: Log scan progressed past the checkpoint lsn 395
:05:28&&InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Error: tried to read 16384 bytes at offset 0 .
InnoDB: Was only able to read -1.
:05:35&&InnoDB: Operating system error number 5 in a file operation.
InnoDB: Error number 5 means 'Input/output error'.
InnoDB: Some operating system error numbers are described at
InnoDB: File operation call: 'read'.
InnoDB: Cannot continue operation.
:05:35 mysqld_safe mysqld from pid file /Databases/mysql/Hawx-01.pid ended
:11:38 mysqld_safe Starting mysqld daemon with databases from /Databases/mysql
:11:38 [Warning] --myisam_max_extra_sort_file_size is deprecated and does nothing in this version.&&It will be removed in a future release.
:11:38 [Note] Plugin 'FEDERATED' is disabled.
:11:38&&InnoDB: Initializing buffer pool, size = 5.0G
:11:39&&InnoDB: Completed initialization of buffer pool
InnoDB: Log scan progressed past the checkpoint lsn 395
:11:39&&InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Error: tried to read 16384 bytes at offset 0 .
InnoDB: Was only able to read -1.
:11:40&&InnoDB: Operating system error number 5 in a file operation.
InnoDB: Error number 5 means 'Input/output error'.
InnoDB: Some operating system error numbers are described at
InnoDB: File operation call: 'read'.
InnoDB: Cannot continue operation.
:11:41 mysqld_safe mysqld from pid file /Databases/mysql/Hawx-01.pid ended
:12:59 mysqld_safe Starting mysqld daemon with databases from /Databases/mysql
:12:59 [Warning] --myisam_max_extra_sort_file_size is deprecated and does nothing in this version.&&It will be removed in a future release.
:12:59 [Note] Plugin 'FEDERATED' is disabled.
:12:59&&InnoDB: Initializing buffer pool, size = 5.0G
:13:00&&InnoDB: Completed initialization of buffer pool
InnoDB: Log scan progressed past the checkpoint lsn 395
:13:00&&InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Error: tried to read 16384 bytes at offset 0 .
InnoDB: Was only able to read -1.
:13:00&&InnoDB: Operating system error number 5 in a file operation.
InnoDB: Error number 5 means 'Input/output error'.
InnoDB: Some operating system error numbers are described at
InnoDB: File operation call: 'read'.
InnoDB: Cannot continue operation.
:13:00 mysqld_safe mysqld from pid file /Databases/mysql/Hawx-01.pid ended
:15:22 mysqld_safe Starting mysqld daemon with databases from /Databases/mysql
:15:22 [Warning] --myisam_max_extra_sort_file_size is deprecated and does nothing in this version.&&It will be removed in a future release.
:15:22 [Note] Plugin 'FEDERATED' is disabled.
:15:22&&InnoDB: Initializing buffer pool, size = 5.0G
:15:23&&InnoDB: Completed initialization of buffer pool
InnoDB: Log scan progressed past the checkpoint lsn 395
:15:23&&InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Error: tried to read 16384 bytes at offset 0 .
InnoDB: Was only able to read -1.
:15:23&&InnoDB: Operating system error number 5 in a file operation.
InnoDB: Error number 5 means 'Input/output error'.
InnoDB: Some operating system error numbers are described at
InnoDB: File operation call: 'read'.
InnoDB: Cannot continue operation.
:15:23 mysqld_safe mysqld from pid file /Databases/mysql/Hawx-01.pid ended
没有人能帮助解答吗？？
InnoDB: Check also that the disk is not full or a disk quota exceeded.
很明显 提示你数据写入不了 首先查看数据库所在的分区是否已满
中级工程师
引用:原帖由 oulinhl 于
09:03 发表
没有人能帮助解答吗？？ Error number 5 means 'Input/output error'. 官方解释为 IO出错，这个可能是磁盘引起的，或者你的表空间已经损坏，排除磁盘的问题后，你可以进行forcing recovery ； 这个链接是官方文档，innodb_force_recovery 从1-4 依次尝试，正常启动后，建立Myisam 表 把你的innodb数据导入到MYisam中，剩下的是，调整 innodb_force_recovery 参数为0 ，恢复表！
引用:原帖由 位鹏飞 于
09:37 发表
Error number 5 means 'Input/output error'. 官方解释为 IO出错，这个可能是磁盘引起的，或者你的表空间已经损坏，排除磁盘的问题后，你可以进行forcing recovery ；/doc/refman/5.1/en/forcing-innodb- ... 不能完全指望innodb_force_recovery来做完全的恢复，平时做好数据备份更保险，对高可用性要求高的话还可以做冗余容灾！！
中级工程师
引用:原帖由 smart818 于
12:04 发表
不能完全指望innodb_force_recovery来做完全的恢复，平时做好数据备份更保险，对高可用性要求高的话还可以做冗余容灾！！ 你说的对，一般的做法 是 innodb_force_recovery 恢复不成功的话，可直接用备份搞定，直接用备份 恢复的话，除非你的备份能保证丢失最少。找lib的vendor解决
UID839105&帖子109&精华0&积分4668&资产4668 信元&发贴收入1355 信元&推广收入0 信元&附件收入1720 信元&下载支出5255 信元&阅读权限50&在线时间676 小时&注册时间&最后登录&
错误信息看看啊？
UID536270&帖子87&精华0&积分5819&资产5819 信元&发贴收入480 信元&推广收入77 信元&附件收入4136 信元&下载支出924 信元&阅读权限120&在线时间106 小时&注册时间&最后登录&
一般情况下如果是fab给 的lib应该不会存在什么语法问题，请确认生成lib的工具版本是否与你导出DB文件工具版本匹配
UID574476&帖子114&精华0&积分16974&资产16974 信元&发贴收入595 信元&推广收入0 信元&附件收入0 信元&下载支出6901 信元&阅读权限70&在线时间626 小时&注册时间&最后登录&
tiger_lein
& & 多谢版主提醒。把整个lib看了一遍（还好不长），实在没实力。只能让向提供lib的人解决了。
UID574476&帖子114&精华0&积分16974&资产16974 信元&发贴收入595 信元&推广收入0 信元&附件收入0 信元&下载支出6901 信元&阅读权限70&在线时间626 小时&注册时间&最后登录&
dummy_tony
& & 提示信息就是说在哪一行或者附近出现语法错误，像这种提示信息，我想你也懂的，根本没用。
UID847560&帖子71&精华0&积分2&资产2 信元&发贴收入395 信元&推广收入0 信元&附件收入0 信元&下载支出474 信元&阅读权限10&在线时间232 小时&注册时间&最后登录&
我用的lc_shell
UID574476&帖子114&精华0&积分16974&资产16974 信元&发贴收入595 信元&推广收入0 信元&附件收入0 信元&下载支出6901 信元&阅读权限70&在线时间626 小时&注册时间&最后登录&
ppseuradio1
& & 多谢关注，不是工具的问题。是那个XXX.lib本身有问题。因为我转换其他的没报错，到那个文件就不行了。
UID378663&帖子7864&精华2&积分184269&资产184269 信元&发贴收入195240 信元&推广收入0 信元&附件收入27280 信元&下载支出2256 信元&阅读权限120&在线时间2104 小时&注册时间&最后登录&
哪里错了 就找哪一行
UID574476&帖子114&精华0&积分16974&资产16974 信元&发贴收入595 信元&推广收入0 信元&附件收入0 信元&下载支出6901 信元&阅读权限70&在线时间626 小时&注册时间&最后登录&
& & 工具提示，总不是那么可靠。我想大侠应该也懂。
[通过 QQ、MSN 分享给朋友]
欢迎访问 TI SLL(信号链)专区}