Percona Server crashes on checksum statement after table import
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS |
Fix Released
|
High
|
Unassigned |
Bug Description
Test case xb_export for Percona XtraBackup causes Percona Server 5.1 crash on checksum table statement.
Reproduced on Ubuntu 10.04 x86_64 w/
5.1.54-12.5
5.1.51-11.5
Backtrace from test log:
110126 2:30:32 InnoDB: Assertion failure in thread 140399065376512 in file row/row0sel.c line 3861
InnoDB: Failing assertion: rec
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.
110126 2:30:32 - 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.
key_buffer_
read_buffer_
max_used_
max_threads=151
threads_connected=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd: 0x17edf30
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 = 0x7fb1346b1ca8 thread_stack 0x40000
/root/xb_
/root/xb_
/lib/libpthread
/lib/libc.
/lib/libc.
/root/xb_
/root/xb_
/root/xb_
/root/xb_
/root/xb_
/root/xb_
/root/xb_
/root/xb_
/root/xb_
/root/xb_
/lib/libpthread
/lib/libc.
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x1845980 = checksum table test
thd->thread_id=6
thd->killed=
The manual page at http://
information that should help you find out what is causing the crash.
Writing a core file
ERROR 2013 (HY000) at line 1: Lost connection to MySQL server during query
t/xb_export.sh: line 48: 922 Aborted (core dumped) ${MYSQLD} ${MYSQLD_ARGS} $* --port=$mysql_port
Please find core dump at http://
Related branches
- Vadim Tkachenko: Approve
- Yasufumi Kinoshita: Pending requested
- Alexey Kopytov: Pending requested
-
Diff: 104 lines (+100/-0)1 file modifiedtest/t/xb_export.sh (+100/-0)
- Valentine Gostev (community): Approve (qa)
- Fred Linhoss (community): Approve (documentation)
- Percona developers: Pending requested
-
Diff: 307 lines (+133/-104)3 files modifiedinnodb_dict_size_limit.patch (+127/-80)
innodb_expand_import.patch (+2/-2)
innodb_split_buf_pool_mutex.patch (+4/-22)
Changed in percona-server: | |
milestone: | none → release-5.1.54-12.5 |
importance: | Undecided → High |
status: | New → Triaged |
assignee: | nobody → Yasufumi Kinoshita (yasufumi-kinoshita) |
description: | updated |
Changed in percona-server: | |
status: | Fix Committed → Fix Released |
I don't know "xb_report".
I cannot do anything for now.
Please assign to the author of the "xb_report"
or add information for other developers to solve if you want to be solved by others.