MySQL Forums
Forum List  »  InnoDB

After a server crash InnoDB can't recover
Date: February 28, 2017 03:26PM

Following from a (Ubuntu) server crash MySQL server won't re-start .. below is an extract from the error log..

Relevant file system has plenty of free space available:-

Filesystem Size Used Avail Use% Mounted on
/dev/md2 1016G 339G 626G 36% /

Not sure on the best way to recover this - any pointers?

Thanks in advance

2017-02-28 22:03:40 0 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
2017-02-28 22:03:40 0 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
2017-02-28 22:03:40 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-02-28 22:03:40 0 [Note] /usr/local/mysql/bin/mysqld (mysqld 5.6.26-log) starting as process 3288 ...
2017-02-28 22:03:40 3288 [Note] Plugin 'FEDERATED' is disabled.
2017-02-28 22:03:40 7f4515839740 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-02-28 22:03:40 3288 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-02-28 22:03:40 3288 [Note] InnoDB: The InnoDB memory heap is disabled
2017-02-28 22:03:40 3288 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-02-28 22:03:40 3288 [Note] InnoDB: Memory barrier is not used
2017-02-28 22:03:40 3288 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-02-28 22:03:40 3288 [Note] InnoDB: Using Linux native AIO
2017-02-28 22:03:40 3288 [Note] InnoDB: Using CPU crc32 instructions
2017-02-28 22:03:40 3288 [Note] InnoDB: Initializing buffer pool, size = 384.0M
2017-02-28 22:03:40 3288 [Note] InnoDB: Completed initialization of buffer pool
2017-02-28 22:03:56 3288 [ERROR] InnoDB: Tried to read 1048576 bytes at offset 2097152. Was only able to read 1011712.
InnoDB: Fatal error: cannot read from file. OS error number 17.
2017-02-28 22:03:56 7f4515839740 InnoDB: Assertion failure in thread 139934690416448 in file line 2692
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to
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: about forcing recovery.
21:03:56 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.

It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1013644 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
The manual page at contains
information that should help you find out what is causing the crash.

Options: ReplyQuote

Written By
After a server crash InnoDB can't recover
February 28, 2017 03:26PM

Sorry, you can't reply to this topic. It has been closed.

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.