InnoDB: Assertion failure in thread <nr> in file fil0fil.c line 844
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS | Status tracked in 5.7 | |||||
5.1 |
Won't Fix
|
Undecided
|
Unassigned | |||
5.5 |
New
|
Undecided
|
Unassigned | |||
5.6 |
New
|
Undecided
|
Unassigned | |||
5.7 |
New
|
Undecided
|
Unassigned |
Bug Description
Testing crash safe slave on PS 5.5.33-29.3
Configure master-slave with slave having following options:
innodb_
innodb_
innodb_
innodb_
log-bin=a
log-slave-
Start slave and sync to master position.
Start RQG against master.
kill -9 slave
Restart slave:
131031 15:27:28 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: Warning: innodb_
InnoDB: relay-log.info is detected.
InnoDB: relay log: position 1579421, file name ./mysql-
InnoDB: master log: position 1579484, file name a.000003
131031 15:27:28 InnoDB: !!!!!!!! UNIV_DEBUG switched on !!!!!!!!!
131031 15:27:28 InnoDB: The InnoDB memory heap is disabled
131031 15:27:28 InnoDB: Mutexes and rw_locks use GCC atomic builtins
131031 15:27:28 InnoDB: Compressed tables use zlib 1.2.3
131031 15:27:28 InnoDB: Using Linux native AIO
131031 15:27:28 InnoDB: Initializing buffer pool, size = 128.0M
131031 15:27:28 InnoDB: Completed initialization of buffer pool
131031 15:27:28 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 24664943
131031 15:27:28 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Unable to lock ./rqg1/
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
131031 15:27:28 InnoDB: Assertion failure in thread 140293712815904 in file fil0fil.c line 844
InnoDB: Failing assertion: ret
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://
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://
InnoDB: about forcing recovery.
22:27:28 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://
key_buffer_
read_buffer_
max_used_
max_threads=153
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_
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(
mysqld(
/lib64/
/lib64/
/lib64/
mysqld[0x8f1e71]
mysqld[0x8f2070]
mysqld[0x8f24ef]
mysqld[0x8f252c]
mysqld[0x8727c3]
mysqld[0x937a58]
mysqld[0x93bf0a]
mysqld[0x93d3a3]
mysqld[0x8579a7]
mysqld[0x80498f]
mysqld(
mysqld[0x5acf80]
mysqld(
mysqld[0x51fc9b]
mysqld(
mysqld(
/lib64/
mysqld[0x515cd9]
You may download the Percona Server operations manual by visiting
http://
in the manual which will help you identify the cause of the crash.
Writing a core file
Changed in percona-server: | |
status: | Incomplete → New |
tags: | added: i38419 |
thread apply all bt