MySQL Forums
Forum List  »  InnoDB

mysql 5.7 crashes on corrupt ibdata1 file
Posted by: Matthijs Tempels
Date: February 26, 2020 08:25AM

Hi,

We have a corrupt database server and sketchy backups at best (sigh)
the only way I can start mysql at the moment is with --innodb_force_recovery=6

the db starts but has tons of errors and i am unable to recover any data..

when i try _any_ option lower than 6 i get:

2020-02-26T14:07:45.323452Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2020-02-26T14:07:45.323557Z 0 [Warning] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
2020-02-26T14:07:45.326256Z 0 [Note] mysqld (mysqld 5.7.29-0ubuntu0.18.04.1) starting as process 10532 ...
2020-02-26T14:07:45.330795Z 0 [Note] InnoDB: PUNCH HOLE support available
2020-02-26T14:07:45.330824Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-02-26T14:07:45.330830Z 0 [Note] InnoDB: Uses event mutexes
2020-02-26T14:07:45.330835Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2020-02-26T14:07:45.330849Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-02-26T14:07:45.330863Z 0 [Note] InnoDB: Using Linux native AIO
2020-02-26T14:07:45.331231Z 0 [Note] InnoDB: Number of pools: 1
2020-02-26T14:07:45.331384Z 0 [Note] InnoDB: Using CPU crc32 instructions
2020-02-26T14:07:45.332999Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2020-02-26T14:07:45.343061Z 0 [Note] InnoDB: Completed initialization of buffer pool
2020-02-26T14:07:45.346902Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2020-02-26T14:07:45.362291Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2020-02-26T14:07:45.364778Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 7734357978003
2020-02-26T14:07:45.497412Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7734363220480
2020-02-26T14:07:45.685779Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7734368463360
2020-02-26T14:07:45.839556Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7734373706240
2020-02-26T14:07:45.927858Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7734377149820
2020-02-26T14:07:45.929022Z 0 [Note] InnoDB: Database was not shutdown normally!
2020-02-26T14:07:45.929055Z 0 [Note] InnoDB: Starting crash recovery.
14:07:45 UTC - 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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68196 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 0x40000
mysqld(my_print_stacktrace+0x3b)[0xeaf22b]
mysqld(handle_fatal_signal+0x48b)[0x7794ab]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x12890)[0x7f3282a52890]
mysqld(_Z23page_cur_insert_rec_lowPhP12dict_index_tPKhPmP5mtr_t+0x338)[0xf7a898]
mysqld(_Z25page_cur_parse_insert_recmPKhS0_P11buf_block_tP12dict_index_tP5mtr_t+0x640)[0xf7c500]
mysqld[0xf54784]
mysqld(_Z22recv_recover_page_funcmP11buf_block_t+0x747)[0xf55577]
mysqld(_Z20buf_page_io_completeP10buf_page_tb+0x30e)[0x10c213e]
mysqld(_Z13buf_read_pageRK9page_id_tRK11page_size_t+0x55a)[0x10f209a]
mysqld(_Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb+0x4e5)[0x10c3915]
mysqld(_Z21ibuf_init_at_db_startv+0x6ad)[0xf32f1d]
mysqld(_Z9dict_bootv+0x9d3)[0x10f5fd3]
mysqld(_Z34innobase_start_or_create_for_mysqlv+0x448a)[0x10315ea]
mysqld[0xef683d]
mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x4f)[0x7cc69f]
mysqld[0xc888c5]
mysqld(_Z40plugin_register_builtin_and_init_core_sePiPPc+0x1e5)[0xc8bde5]
mysqld[0x771770]
mysqld(_Z11mysqld_mainiPPc+0x795)[0x772e75]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7f3281d31b97]
mysqld(_start+0x2a)[0x76921a]
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.

so mysql segfaults and I have no idea what to do about it

short question: HELP? :-/

Cheers

Matthijs

Options: ReplyQuote


Subject
Views
Written By
Posted
mysql 5.7 crashes on corrupt ibdata1 file
70
February 26, 2020 08:25AM


Sorry, only registered users may post in this forum.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.