InnoDB: Database page corruption on disk or a failed
|
InnoDB: space 0 file ./ibdata1 read of page 7.
|
InnoDB: You may have to recover from a backup.
|
2015-07-02 10:01:16 7fa4f1ade780 InnoDB: Page dump in ascii and hex (16384 bytes):
|
len 16384; hex 455013d40000000700000000000000000000000000....
|
InnoDB: End of page dump
|
2015-07-02 10:01:17 7fa4f1ade780 InnoDB: uncompressed page, stored checksum in field1 1162875860, calculated checksums for field1: crc32 108430924, innodb 4033652427, none 3735928559, stored checksum in field2 624286960, calculated checksums for field2: crc32 108430924, innodb 624286960, none 3735928559, page LSN 0 1739463, low 4 bytes of LSN at page end 1739463, page number (if stored to page already) 7, space id (if created with >= MySQL-4.1.1 and stored already) 0
|
InnoDB: page type 393216 meaning PAGE TYPE CORRUPTED
|
InnoDB: Page may be a system page
|
InnoDB: Database page corruption on disk or a failed
|
InnoDB: file read of page 7.
|
InnoDB: You may have to recover from a backup.
|
InnoDB: It is also possible that your operating
|
InnoDB: system has corrupted its own file cache
|
InnoDB: and rebooting your computer removes the
|
InnoDB: error.
|
InnoDB: If the corrupt page is an index page
|
InnoDB: you can also try to fix the corruption
|
InnoDB: by dumping, dropping, and reimporting
|
InnoDB: the corrupt table. You can use CHECK
|
InnoDB: TABLE to scan your table for corruption.
|
InnoDB: See also http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
|
InnoDB: about forcing recovery.
|
InnoDB: Ending processing because of a corrupt database page.
|
2015-07-02 10:01:17 7fa4f1ade780 InnoDB: Assertion failure in thread 140346406070144 in file buf0buf.cc line 4513
|
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.
|
150702 10:01:17 [ERROR] 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.
|
|
To report this bug, see http://kb.askmonty.org/en/reporting-bugs
|
|
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.
|
|
Server version: 10.1.6-MariaDB-debug
|
key_buffer_size=134217728
|
read_buffer_size=131072
|
max_used_connections=0
|
max_threads=153
|
thread_count=0
|
It is possible that mysqld could use up to
|
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467186 K bytes of memory
|
Hope that's ok; if not, decrease some variables in the equation.
|
|
Thread pointer: 0x0x0
|
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 = 0x0 thread_stack 0x48000
|
addr2line: 'sql/mysqld': No such file
|
sql/mysqld(my_print_stacktrace+0x38)[0x7fa4f28455be]
|
sql/mysqld(handle_fatal_signal+0x34c)[0x7fa4f222d603]
|
/lib/x86_64-linux-gnu/libpthread.so.0(+0x10340)[0x7fa4f0002340]
|
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x39)[0x7fa4ef659cc9]
|
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7fa4ef65d0d8]
|
sql/mysqld(+0xc077c0)[0x7fa4f27227c0]
|
sql/mysqld(+0xc252dc)[0x7fa4f27402dc]
|
sql/mysqld(+0xc25724)[0x7fa4f2740724]
|
sql/mysqld(+0xc03985)[0x7fa4f271e985]
|
sql/mysqld(+0xc2c817)[0x7fa4f2747817]
|
sql/mysqld(+0xc2ce6d)[0x7fa4f2747e6d]
|
sql/mysqld(+0xb742ac)[0x7fa4f268f2ac]
|
sql/mysqld(+0xa0c21f)[0x7fa4f252721f]
|
sql/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0xf3)[0x7fa4f222f55a]
|
sql/mysqld(+0x4fec05)[0x7fa4f2019c05]
|
sql/mysqld(_Z11plugin_initPiPPci+0x8e5)[0x7fa4f201a7c8]
|
sql/mysqld(+0x3e37ba)[0x7fa4f1efe7ba]
|
sql/mysqld(_Z11mysqld_mainiPPc+0x5f3)[0x7fa4f1eff750]
|
sql/mysqld(main+0x20)[0x7fa4f1ef51d5]
|
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7fa4ef644ec5]
|
sql/mysqld(+0x3da0c8)[0x7fa4f1ef50c8]
|
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.
|