免费注册 查看新帖 |

Chinaunix

  平台 论坛 博客 文库
最近访问板块 发新帖
查看: 2101 | 回复: 1

Mysql错误:紧急救助!!! [复制链接]

论坛徽章:
0
发表于 2013-06-24 17:07 |显示全部楼层
各位,紧急求助,刚刚监控到Mysql服务宕了,由于本人对Mysql还不是很熟悉,请大家协助,错误日志如下:

130624 16:05:23  InnoDB: Error: Write to file /Databases/mysql/ibdata1 failed at offset 0 536870912.
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
InnoDB: http://dev.mysql.com/doc/refman/ ... em-error-codes.html
130624 16:05:24  InnoDB: Assertion failure in thread 1139128640 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 http://bugs.mysql.com.
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: http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html
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=33554432
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's ok; 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)[0x3b32830265]
/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 http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
130624 16:05:25 mysqld_safe Number of processes running now: 0
130624 16:05:26 mysqld_safe mysqld restarted
130624 16: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.
130624 16:05:26 [Note] Plugin 'FEDERATED' is disabled.
130624 16:05:27  InnoDB: Initializing buffer pool, size = 5.0G
130624 16:05:27  InnoDB: Completed initialization of buffer pool
InnoDB: Log scan progressed past the checkpoint lsn 395 1619918680
130624 16: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 536870912.
InnoDB: Was only able to read -1.
130624 16: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: http://dev.mysql.com/doc/refman/ ... em-error-codes.html
InnoDB: File operation call: 'read'.
InnoDB: Cannot continue operation.
130624 16:05:35 mysqld_safe mysqld from pid file /Databases/mysql/Hawx-01.pid ended
130624 16:11:38 mysqld_safe Starting mysqld daemon with databases from /Databases/mysql
130624 16: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.
130624 16:11:38 [Note] Plugin 'FEDERATED' is disabled.
130624 16:11:38  InnoDB: Initializing buffer pool, size = 5.0G
130624 16:11:39  InnoDB: Completed initialization of buffer pool
InnoDB: Log scan progressed past the checkpoint lsn 395 1619918680
130624 16: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 536870912.
InnoDB: Was only able to read -1.
130624 16: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: http://dev.mysql.com/doc/refman/ ... em-error-codes.html
InnoDB: File operation call: 'read'.
InnoDB: Cannot continue operation.
130624 16:11:41 mysqld_safe mysqld from pid file /Databases/mysql/Hawx-01.pid ended
130624 16:12:59 mysqld_safe Starting mysqld daemon with databases from /Databases/mysql
130624 16: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.
130624 16:12:59 [Note] Plugin 'FEDERATED' is disabled.
130624 16:12:59  InnoDB: Initializing buffer pool, size = 5.0G
130624 16:13:00  InnoDB: Completed initialization of buffer pool
InnoDB: Log scan progressed past the checkpoint lsn 395 1619918680
130624 16: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 536870912.
InnoDB: Was only able to read -1.
130624 16: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: http://dev.mysql.com/doc/refman/ ... em-error-codes.html
InnoDB: File operation call: 'read'.
InnoDB: Cannot continue operation.
130624 16:13:00 mysqld_safe mysqld from pid file /Databases/mysql/Hawx-01.pid ended
130624 16:15:22 mysqld_safe Starting mysqld daemon with databases from /Databases/mysql
130624 16: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.
130624 16:15:22 [Note] Plugin 'FEDERATED' is disabled.
130624 16:15:22  InnoDB: Initializing buffer pool, size = 5.0G
130624 16:15:23  InnoDB: Completed initialization of buffer pool
InnoDB: Log scan progressed past the checkpoint lsn 395 1619918680
130624 16: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 536870912.
InnoDB: Was only able to read -1.
130624 16: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: http://dev.mysql.com/doc/refman/ ... em-error-codes.html
InnoDB: File operation call: 'read'.
InnoDB: Cannot continue operation.
130624 16:15:23 mysqld_safe mysqld from pid file /Databases/mysql/Hawx-01.pid ended

论坛徽章:
16
IT运维版块每日发帖之星
日期:2015-10-02 06:20:00IT运维版块每月发帖之星
日期:2015-09-11 19:30:52IT运维版块每周发帖之星
日期:2015-09-11 19:20:31IT运维版块每日发帖之星
日期:2015-08-26 06:20:00每日论坛发贴之星
日期:2015-08-20 06:20:00IT运维版块每日发帖之星
日期:2015-08-20 06:20:002015年辞旧岁徽章
日期:2015-03-03 16:54:15金牛座
日期:2014-05-04 16:58:09双子座
日期:2013-12-17 16:44:37辰龙
日期:2013-11-22 15:20:59狮子座
日期:2013-11-18 22:55:08射手座
日期:2013-11-12 10:54:26
发表于 2013-06-25 09:00 |显示全部楼层
1>InnoDB: Check that your OS and file system support files of this size.
2>InnoDB: Check also that the disk is not full or a disk quota exceeded.
3>InnoDB: Error number 5 means 'Input/output error'.
4>http://dev.mysql.com/doc/refman/ ... em-error-codes.html
您需要登录后才可以回帖 登录 | 注册

本版积分规则 发表回复

  

北京盛拓优讯信息技术有限公司. 版权所有 京ICP备16024965号-6 北京市公安局海淀分局网监中心备案编号:11010802020122 niuxiaotong@pcpop.com 17352615567
未成年举报专区
中国互联网协会会员  联系我们:huangweiwei@itpub.net
感谢所有关心和支持过ChinaUnix的朋友们 转载本站内容请注明原作者名及出处

清除 Cookies - ChinaUnix - Archiver - WAP - TOP