mysqldump 导入数据，innodb 崩溃
debian7percona mysql 5.6
日志如下，这个如何破解？ 谢谢
150806 01:27:05 mysqld_safe Starting mysqld daemon with databases from /srv/mysql
2015-08-06 01:27:06 0 Using unique option prefix group instead of group_concat_max_len is deprecated and will be removed in a future release. Please use the
full name instead.
2015-08-06 01:27:06 0 option 'group_concat_max_len': unsigned value 0 adjusted to 4
2015-08-06 01:27:06 0 /opt/mysql/bin/mysqld (mysqld 5.6.25-73.1-log) starting as process 19849 ...
2015-08-06 01:27:06 19849 Plugin 'FEDERATED' is disabled.
2015-08-06 01:27:06 19849 InnoDB: Using atomics to ref count buffer pool pages
2015-08-06 01:27:06 19849 InnoDB: The InnoDB memory heap is disabled
2015-08-06 01:27:06 19849 InnoDB: Mutexes and rw_locks use GCC atomic builtins
2015-08-06 01:27:06 19849 InnoDB: Memory barrier is not used
2015-08-06 01:27:06 19849 InnoDB: Compressed tables use zlib 1.2.3
2015-08-06 01:27:06 19849 InnoDB: Using Linux native AIO
2015-08-06 01:27:06 19849 InnoDB: Using CPU crc32 instructions
2015-08-06 01:27:06 19849 InnoDB: Initializing buffer pool, size = 32.0G
2015-08-06 01:27:08 19849 InnoDB: Completed initialization of buffer pool
2015-08-06 01:27:08 19849 InnoDB: Highest supported file format is Barracuda.
2015-08-06 01:27:09 19849 InnoDB: 128 rollback segment(s) are active.
2015-08-06 01:27:09 19849 InnoDB: Waiting for purge to start
2015-08-06 01:27:09 19849 InnoDB:Percona XtraDB (http://www.percona.com) 5.6.25-73.1 started; log sequence number 1625988
2015-08-06 01:27:09 19849 No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID:
33587c9d-3b97-11e5-921b-44a8422329db.
2015-08-06 01:27:09 19849 Server hostname (bind-address): '*'; port: 3306
2015-08-06 01:27:09 19849 IPv6 is available.
2015-08-06 01:27:09 19849 - '::' resolves to '::';
2015-08-06 01:27:09 19849 Server socket created on IP: '::'.
2015-08-06 01:27:09 19849 'user' entry 'root@db' ignored in --skip-name-resolve mode.
2015-08-06 01:27:09 19849 'user' entry '@db' ignored in --skip-name-resolve mode.
2015-08-06 01:27:09 19849 'proxies_priv' entry '@ root@db' ignored in --skip-name-resolve mode.
2015-08-06 01:27:09 19849 Event Scheduler: Loaded 0 events
2015-08-06 01:27:09 19849 /opt/mysql/bin/mysqld: ready for connections.
Version: '5.6.25-73.1-log'socket: '/tmp/mysql.sock'port: 3306Source distribution
2015-08-06 03:46:51 7f4be7fff700InnoDB: Assertion failure in thread 139963991586560 in file rem0rec.cc line 577
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/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
19:46:51 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.
Please help us make Percona Server better by reporting any
bugs at http://bugs.percona.com/
key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=2
max_threads=2002
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 = 804551 Kbytes 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 0x40000
/opt/mysql/bin/mysqld(my_print_stacktrace+0x2e)
/opt/mysql/bin/mysqld(handle_fatal_signal+0x36c)
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf0a0)
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35)
/lib/x86_64-linux-gnu/libc.so.6(abort+0x180)
/opt/mysql/bin/mysqld
/opt/mysql/bin/mysqld
/opt/mysql/bin/mysqld
/opt/mysql/bin/mysqld
/opt/mysql/bin/mysqld
/opt/mysql/bin/mysqld
/lib/x86_64-linux-gnu/libpthread.so.0(+0x6b50)
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)
You may download the Percona Server operations manual by visiting
http://www.percona.com/software/percona-server/. You may find information
in the manual which will help you identify the cause of the crash.
150806 03:46:54 mysqld_safe Number of processes running now: 0
150806 03:46:54 mysqld_safe mysqld restarted
2015-08-06 03:46:55 0 Using unique option prefix group instead of group_concat_max_len is deprecated and will be removed in a future release. Please use the
full name instead.
2015-08-06 03:46:55 0 option 'group_concat_max_len': unsigned value 0 adjusted to 4
2015-08-06 03:46:55 0 /opt/mysql/bin/mysqld (mysqld 5.6.25-73.1-log) starting as process 23069 ...
2015-08-06 03:46:55 23069 Plugin 'FEDERATED' is disabled.
2015-08-06 03:46:55 23069 InnoDB: Using atomics to ref count buffer pool pages
2015-08-06 03:46:55 23069 InnoDB: The InnoDB memory heap is disabled
2015-08-06 03:46:55 23069 InnoDB: Mutexes and rw_locks use GCC atomic builtins
2015-08-06 03:46:55 23069 InnoDB: Memory barrier is not used
2015-08-06 03:46:55 23069 InnoDB: Compressed tables use zlib 1.2.3
2015-08-06 03:46:55 23069 InnoDB: Using Linux native AIO
2015-08-06 03:46:55 23069 InnoDB: Using CPU crc32 instructions
2015-08-06 03:46:55 23069 InnoDB: Initializing buffer pool, size = 32.0G
2015-08-06 03:46:57 23069 InnoDB: Completed initialization of buffer pool
2015-08-06 03:46:58 23069 InnoDB: Highest supported file format is Barracuda.
2015-08-06 03:46:58 23069 InnoDB: Log scan progressed past the checkpoint lsn 59680535024
2015-08-06 03:46:58 23069 InnoDB: Database was not shutdown normally!
2015-08-06 03:46:58 23069 InnoDB: Starting crash recovery.
2015-08-06 03:46:58 23069 InnoDB: Reading tablespace information from the .ibd files...
2015-08-06 03:46:58 23069 InnoDB: Restoring possible half-written data pages
2015-08-06 03:46:58 23069 InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 59685777408 2015-08-06 03:46:58 23069 InnoDB: Database was not shutdown normally! /opt/mysql/bin/mysqld(handle_fatal_signal+0x36c)
看看当时的内存够不够用，是不是oom了 回复 3# visician
不是内存的问题，内存很大的。 应该和DUMP没关系啊。
页:
[1]