I also found that if NOTPM is very high(40k-50k) when backup, the crash is more likely to happen. If the dbt2 TPM is 10k-20k-30k, the crash seldom happened. MySQL version : 5.0.75 DBT2: dbt2-0.40 Data is stored on SSDs, logs on HD. my.cnf : default-storage-engine=innodb innodb_file_per_table innodb_buffer_pool_size = 16G innodb_additional_mem_pool_size = 20M ## Set .._log_file_sizie to 25 % of buffer pool size innodb_log_file_size = 1G innodb_log_buffer_size = 16M innodb_flush_log_at_trx_commit = 1 innodb_flush_method = O_DIRECT error message: InnoDB: Error (2): trying to extend a single-table tablespace 3 InnoDB: by single page(s) though the space size 23360. Page no 23360. 091027 12:52:44InnoDB: Error: trying to access a stray pointer (nil) InnoDB: buf pool start is at 0x7f3f35880000, end at 0x7f4335880000 InnoDB: Probable reason is database corruption or memory InnoDB: corruption. If this happens in an InnoDB database recovery, see InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html InnoDB: how to force recovery. 091027 12:52:44InnoDB: Assertion failure in thread 1088379200 in file ./../include/buf0buf.ic line 232 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. 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://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html InnoDB: about forcing recovery. 091027 12:52:44 - 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. 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_size=134217728 read_buffer_size=1048576 max_used_connections=33 max_connections=1000 threads_connected=33 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 3203064 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x20422df0 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... Cannot determine thread, fp=0x40df50e0, backtrace may not be correct. Bogus stack limit or frame pointer, fp=0x40df50e0, stack_bottom=0x40df0000, thread_stack=262144, aborting backtrace. Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 0x7f3ee6324628 is invalid pointer thd->thread_id=23 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. Writing a core file ./bin/mysqld_safe: line 388: 20914 Segmentation fault (core dumped) nohup /usr/local/mysql-5.0/libexec/mysqld --defaults-file=/opt/schooner/mysql/config/my.cnf --basedir=/usr/local/mysql-5.0 --datadir=/schooner/data/db0 --user=root --pid-file=/schooner/data/db0/localhost.localdomain.pid --skip-external-locking --port=3307 --socket=/schooner/data/db0/mysql.sock >> /schooner/data/db0/localhost.localdomain.err 2>&1 Number of processes running now: 0 091027 12:52:49 mysqld restarted Number of processes running now: 0 091027 12:52:49 mysqld restarted InnoDB: Log scan progressed past the checkpoint lsn 0 1499062839 091027 12:52:53 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: Doing recovery: scanned up to log sequence number 0 1501767928 InnoDB: 7 transaction(s) which must be rolled back or cleaned up InnoDB: in total 88 row operations to undo InnoDB: Trx id counter is 0 257536 091027 12:52:55 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed InnoDB: Starting in background the rollback of uncommitted transactions 091027 12:53:19 InnoDB: Rolling back trx with id 0 257072, 4 rows to undo 091027 12:53:19 InnoDB: Started; log sequence number 0 1501767928 InnoDB: Rolling back of trx id 0 257072 completed 091027 12:53:19 InnoDB: Rolling back trx with id 0 257069, 6 rows to undo InnoDB: Rolling back of trx id 0 257069 completed 091027 12:53:19 InnoDB: Rolling back trx with id 0 257065, 12 rows to undo InnoDB: Rolling back of trx id 0 257065 completed 091027 12:53:19 InnoDB: Rolling back trx with id 0 257062, 24 rows to undo InnoDB: Rolling back of trx id 0 257062 completed 091027 12:53:19 InnoDB: Rolling back trx with id 0 257058, 6 rows to undo InnoDB: Rolling back of trx id 0 257058 completed 091027 12:53:19 InnoDB: Rolling back trx with id 0 257057, 16 rows to undo InnoDB: Rolling back of trx id 0 257057 completed 091027 12:53:19 InnoDB: Rolling back trx with id 0 257054, 20 rows to undo InnoDB: Rolling back of trx id 0 257054 completed 091027 12:53:19 InnoDB: Rollback of non-prepared transactions completed 091027 12:53:19 [Note] /usr/local/mysql-5.0/libexec/mysqld: ready for connections. Version: '5.0.75' socket: '/schooner/data/db0/mysql.sock' port: 3307 Source distribution