Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

256GB RAM, 64 Core , AMD running Ubuntu 12.04 with Percona MySQL 5.5.28.

Below is the assertion failure. We just had a second assertion failure (different "in file", position, etc) while running a large set of inserts.

After the first failure, MySQL restarted after a reboot only - after continuously looping on the same error after trying to recover.

I decided to do a mysqlcheck with -o for optimize. Since these are all Innodb tables (very large tables, 60+GB) this would do an alter table on all tables.

In the middle of this , the below assertion failure happened again:

121115 22:30:31  InnoDB: Assertion failure in thread 140086589445888 in file btr0pcur.c line 452
InnoDB: Failing assertion: btr_page_get_prev(next_page, mtr) == buf_block_get_page_no(btr_pcur_get_block(cursor))
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.
03:30:31 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

It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1618416 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x14edeb710
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 = 7f687366ce80 thread_stack 0x30000

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f6300004b60): is an invalid pointer
Connection ID (thread ID): 876

You may download the Percona Server operations manual by visiting You may find information
in the manual which will help you identify the cause of the crash.
121115 22:31:07 [Note] Plugin 'FEDERATED' is disabled.
121115 22:31:07 InnoDB: The InnoDB memory heap is disabled
121115 22:31:07 InnoDB: Mutexes and rw_locks use GCC atomic builtins

.. Then it recovered , without a reboot this time. from the log, what would cause this?

I am currently running a dump to see if the problem resurfaces. - mysqldump completed fine. I am now trying to restore the entire database from the dump.

edit: data partition is all in / since this is a hosted, defaulted file system unfortunately:

Filesystem      Size  Used Avail Use% Mounted on
/dev/vda3       742G  445G  260G  64% /
udev            121G  4.0K  121G   1% /dev
tmpfs            49G  248K   49G   1% /run
none            5.0M     0  5.0M   0% /run/lock
none            121G     0  121G   0% /run/shm
/dev/vda1        99M   54M   40M  58% /boot


port            = 3306
socket          = /var/run/mysqld/mysqld.sock

socket          = /var/run/mysqld/mysqld.sock
nice            = 0


user            = mysql
socket          = /var/run/mysqld/mysqld.sock
port            = 3306
basedir         = /usr
datadir         = /data/mysql
tmpdir          = /tmp

key_buffer              = 512M
max_allowed_packet      = 128M
thread_stack            = 192K
thread_cache_size       = 64

myisam-recover         = BACKUP
max_connections        = 500
table_cache            = 812
table_definition_cache = 812

#query_cache_limit       = 4M
#query_cache_size        = 512M
join_buffer_size        = 512K

innodb_additional_mem_pool_size = 20M
innodb_buffer_pool_size = 196G
#innodb_file_io_threads = 4
#innodb_thread_concurrency = 12
innodb_flush_log_at_trx_commit = 1
innodb_log_buffer_size = 8M
innodb_log_file_size = 1024M
innodb_log_files_in_group = 2
innodb_max_dirty_pages_pct = 90
innodb_lock_wait_timeout = 120

log_error                = /var/log/mysql/error.log

long_query_time =       5
slow_query_log  =       1
slow_query_log_file     =       /var/log/mysql/slowlog.log

max_allowed_packet      = 16M


key_buffer              = 16M

EDIT: the mysqldump completed without issues. Why would these crashes occur on an alter table?

share|improve this question
posting your my.cnf and data partition details may help – thinice Nov 16 '12 at 4:03
done. I have posted the my.cnf and partition table. – Tom Geee Nov 16 '12 at 5:28
As the error would suggest, table space corruption, since an alter is going to touch the whole table space. It smells like a possible hardware issue, have you run diagnostics on the array/each disk and the controller? – thinice Nov 16 '12 at 13:54
I will have to get my host to do that. This is on a dedicated hosted system. thanks for the input. – Tom Geee Nov 16 '12 at 17:15
The output from dmesg or /var/log/messages would likely be helpful as well – kormoc Jan 22 '13 at 21:33

I had a similar crash in the same line of code, with little explanation as to why.

Opened this bug with Percona:

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.