MySQL 5.6.34 sudden outage, boot not, prompt [ERROR] innodb:space ID in FSP header

First, the problem description

A line from the server, in the middle of the night to receive alarm SMS prompt abnormal, connected to the server, found mysqld process is not, PS view, also did not find. So restart, but reboot failed, prompted without PID file then view errorlog, the content is as follows:

2017-09-22 03:37:42 0 [note] --secure-file-priv is set to null.  operations related to importing and exporting data are  disabled2017-09-22 03:37:42 0 [note] /opt/app/mysql5/bin/mysqld  (mysqld 5.6.34- LOG)  starting as process 166408&nbsp, .... 2017-09-22 03:37:42 166408 [note] plugin  ' Federated '  is disabled.2017-09-22  03:37:42 7f5b77946720 innodb: warning: using innodb_additional_mem_pool_size  is DEPRECATED. This option may be removed in future  Releases, together with the option innodb_use_sys_malloc and with the  innodb ' s internal memory allocator.2017-09-22 03:37:42 166408 [note]  Innodb: using atomics to ref count buffer pool pAges2017-09-22 03:37:42 166408 [note] innodb: the innodb memory heap  is disabled2017-09-22 03:37:42 166408 [note] innodb: mutexes and  rw_locks use gcc atomic builtins2017-09-22 03:37:42 166408 [note]  innodb: memory barrier is not used2017-09-22 03:37:42 166408 [ note] innodb: compressed tables use zlib 1.2.32017-09-22 03:37:42  166408 [note] innodb: using cpu crc32 instructions2017-09-22 03:37:42  166408 [note] innodb: initializing buffer pool, size = 4.0g2017-09-22  03:37:43 166408 [note] innodb: completed initialization of buffer  pool2017-09-22 03:37:43 166408 [note] innodb: highest supported file  format is barracuDa.2017-09-22 03:37:43 166408 [note] innodb: log scan progressed past  the checkpoint lsn 40142270189622017-09-22 03:37:43 166408 [Note]  innodb: database was not shutdown normally!2017-09-22 03:37:43 166408  [Note] innodb: starting crash recovery.2017-09-22 03:37:43 166408 [note]  innodb: reading tablespace information from the .ibd files ... 2017-09-22 03:37:43 166408 [error] innodb: space id in fsp header  1416128883,but in the page header 82419585019:37:43 utc - mysqld  got signal 11 ; this could be because you hit a bug. it is also  possible that this binaryor 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 helpdiagnose the problem, but since we have already  crashed, something is definitely wrong and this may fail.key_ Buffer_size=536870912read_buffer_size=16777216max_used_connections=0max_threads=1024thread_count=0connection_ Count=0it is possible that mysqld could use up to key_buffer_size  +  (read_buffer_size + sort_buffer_size) *max_threads = 84423448 k   bytes of memoryhope that ' s ok; if not, decrease some  Variables in the equation. Thread poInter: 0x0attempting backtrace. you can use the following information  to find outwhere mysqld died. If you see no messages  After this, something wentterribly wrong...stack_bottom = 0 thread_stack  0x40000/opt/app/mysql5/bin/mysqld (my_print_stacktrace+0x35) [0x8eebe5]/opt/app/mysql5/bin/mysqld (Handle_ fatal_signal+0x41b) [0x6556ab]/lib64/libpthread.so.0[0x3ff300f7e0]/opt/app/mysql5/bin/mysqld[0xb3366b]/opt/app/ mysql5/bin/mysqld[0x9a240d]/opt/app/mysql5/bin/mysqld[0xa49e6b]/opt/app/mysql5/bin/mysqld[0xa89e06]/opt/app/ mysql5/bin/mysqld[0xa8c0ab]/opt/app/mysql5/bin/mysqld[0xa908c7]/opt/app/mysql5/bin/mysqld[0xa95502]/opt/app/ mysql5/bin/mysqld[0x9844ec]/opt/app/mysql5/bin/mysqld[0x989bab]/opt/app/mysql5/bin/mysqld[0x9fe679]/opt/app/ Mysql5/bin/mysqld[0x94acd7]/opt/app/mysql5/bin/mysqld (_z24ha_initialize_handlertonp13st_plugin_int+0x48) [ 0x590798]/opt/app/mysql5/biN/mysqld[0x6e8716]/opt/app/mysql5/bin/mysqld (_z11plugin_initpippci+0xb3e) [0x6ebf2e]/opt/app/mysql5/bin/mysqld[ 0x583b85]/opt/app/mysql5/bin/mysqld (_Z11MYSQLD_MAINIPPC+0X4D8) [0x588c28]/lib64/libc.so.6 (__libc_start_main+ 0XFD) [0x3ff2c1ed1d]/opt/app/mysql5/bin/mysqld[0x57a8c9]the manual page at http:// Dev.mysql.com/doc/mysql/en/crashing.html containsinformation that should help you  find out what is causing the crash.170922 03:37:43 mysqld_safe  mysqld from pid file /opt/app/mysql5/var/mysql.pid ended170922 04:08:37  mysqld_safe starting mysqld daemon with databases from /opt/app/ Mysql5/var2017-09-22 04:08:37 0 [warning] timestamp with implicit default  value is deprecated. please use --explicit_defaults_for_timestamp server  option  (See documentatioN for more details). Similarly, the use of/opt/app/mysql5/bin/mysqld_safe is not bootable. Online to find a lot of information, there is said to be full of disk is full of memory, but this server's disk and memory are sufficient. Some say is to delete the data directory under the Ibdata and Ib_logfile files, and then restart the OK, but after the test will still not start. Refer to a few links: Analysis connection: Http://qkxue.net/info/155788/MySQL feeling analysis is quite reasonable, but there is no solution!

If any friend has met and successfully resolved, please advise, greatly appreciated!

This article is from the "Knowledge System" blog, please be sure to keep this source http://linuxg.blog.51cto.com/4410110/1967689

MySQL 5.6.34 sudden outage, boot not, prompt [ERROR] innodb:space ID in FSP header