mysql执行大记录语句失败,重启机器后,无法启动

[复制链接]
查看11 | 回复4 | 2015-3-6 11:57:31 | 显示全部楼层 |阅读模式
紧急求助:

091010 19:14:36 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
091010 19:14:36 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: Log scan progressed past the checkpoint lsn 80 3230008271
091010 19:14:36InnoDB: 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: Doing recovery: scanned up to log sequence number 80 3230885509
InnoDB: Transaction 0 334878795 was in the XA prepared state.
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 0 row operations to undo
InnoDB: Trx id counter is 0 334879232
091010 19:14:37InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 091010 19:14:37 - mysqld got signal 11 ;
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=0
max_threads=300
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 3106675 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd: 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 = (nil) thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x21)[0x848ec31]
/usr/sbin/mysqld(handle_segfault+0x37f)[0x81e4b3f]
[0x533420]
/usr/sbin/mysqld(page_cur_insert_rec_low+0x332)[0x83d2652]
/usr/sbin/mysqld(page_cur_parse_insert_rec+0x2f0)[0x83d30f0]
/usr/sbin/mysqld[0x83c1863]
/usr/sbin/mysqld(recv_recover_page+0x350)[0x83c3380]
/usr/sbin/mysqld(buf_page_io_complete+0x579)[0x837fd29]
/usr/sbin/mysqld(fil_aio_wait+0x13b)[0x839a7bb]
/usr/sbin/mysqld[0x83ff8e8]
/lib/libpthread.so.0[0xb7146b]
/lib/libc.so.6(clone+0x5e)[0xac8dbe]
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.
091010 19:14:37 mysqld_safe mysqld from pid file /var/lib/mysql/localhost.localdomain.pid ended
回复

使用道具 举报

千问 | 2015-3-6 11:57:31 | 显示全部楼层
看到此信息:
InnoDB: Progress in percents: 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 091010 19:14:37 - mysqld got signal 11 ;
perror 11的信息:
OS error code11:Resource temporarily unavailable
回复

使用道具 举报

千问 | 2015-3-6 11:57:31 | 显示全部楼层
启动过程,在进行恢复的时候,其他连接是无法连上的,所以内存资源等应该不是问题。
由于是异常关闭,可能有大表损坏需要进行修复,为此磁盘空间,可能不足够.......因为修复的时候会拷贝一份
LZ按这个思路去检查下看
回复

使用道具 举报

千问 | 2015-3-6 11:57:31 | 显示全部楼层
This error can also be caused by malfunctioning hardware.
磁盘故障?
回复

使用道具 举报

千问 | 2015-3-6 11:57:31 | 显示全部楼层
key_buffer_size=33554432
read_buffer_size=2097152
max_used_connections=0
max_threads=300
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 3106675 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

是不是有调整了存储的内存参数,如innodb buffer pool size?
回复

使用道具 举报

您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

主题

0

回帖

4882万

积分

论坛元老

Rank: 8Rank: 8

积分
48824836
热门排行