I'm not really totally sure but does this stack trace is related to the above bug please ? :
xtrabackup version 2.2.10 based on MySQL server 5.6.22 Linux (x86_64) (revision id: )
xtrabackup: cd to /data/mysql
xtrabackup: This target seems to be not prepared yet.
2015-04-10 18:02:13 7fe076d33740 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
xtrabackup: Warning: cannot open ./xtrabackup_logfile. will try to find.
xtrabackup: 'ib_logfile0' seems to be 'xtrabackup_logfile'. will retry.
xtrabackup: xtrabackup_logfile detected: size=2981888, start_lsn=(2529057519583)
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup: innodb_data_home_dir = ./
xtrabackup: innodb_data_file_path = ibdata1:10M:autoextend
xtrabackup: innodb_log_group_home_dir = ./
xtrabackup: innodb_log_files_in_group = 1
xtrabackup: innodb_log_file_size = 2981888
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup: innodb_data_home_dir = ./
xtrabackup: innodb_data_file_path = ibdata1:10M:autoextend
xtrabackup: innodb_log_group_home_dir = ./
xtrabackup: innodb_log_files_in_group = 1
xtrabackup: innodb_log_file_size = 2981888
xtrabackup: Starting InnoDB instance for recovery.
xtrabackup: Using 104857600 bytes for buffer pool (set by --use-memory parameter)
InnoDB: Using atomics to ref count buffer pool pages
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Memory barrier is not used
InnoDB: Compressed tables use zlib 1.2.7
InnoDB: Using CPU crc32 instructions
InnoDB: Initializing buffer pool, size = 100.0M
InnoDB: Completed initialization of buffer pool
InnoDB: Highest supported file format is Barracuda.
InnoDB: The log sequence numbers 2387850439738 and 2387850439738 in ibdata files do not match the log sequence number 2529057519583 in the ib_logfiles!
InnoDB: Database was not shutdown normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages
InnoDB: from the doublewrite buffer...
InnoDB: 128 rollback segment(s) are active.
InnoDB: Waiting for purge to start
16:02:13 UTC - xtrabackup got signal 11 ;
This could be because you hit a bug or data is corrupted.
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.
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 0x10000
InnoDB: 5.6.22 started; log sequence number 2529057519583
xtrabackup(my_print_stacktrace+0x2b) [0x8ed1db]
xtrabackup(handle_fatal_signal+0x252) [0x799202]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf8d0) [0x7fe07691f8d0]
xtrabackup(THD::raise_condition(unsigned int, char const*, Sql_condition::enum_warning_level, char const*)+0x22) [0x7d3f12]
xtrabackup(push_warning_printf(THD*, Sql_condition::enum_warning_level, unsigned int, char const*, ...)+0xb9) [0x886359]
xtrabackup(ib_warn_row_too_big(dict_table_t const*)+0x7f) [0x69bc6f]
xtrabackup(dict_index_add_to_cache(dict_table_t*, dict_index_t*, unsigned long, unsigned long)+0x94b) [0x72854b]
xtrabackup() [0x6a366b]
xtrabackup(dict_load_table(char const*, unsigned long, dict_err_ignore_t)+0xb7e) [0x6a10fe]
xtrabackup(dict_load_foreigns(char const*, char const**, bool, bool, dict_err_ignore_t)+0x1b4c) [0x6a043c]
xtrabackup(dict_load_table(char const*, unsigned long, dict_err_ignore_t)+0xea5) [0x6a1425]
xtrabackup(dict_load_foreigns(char const*, char const**, bool, bool, dict_err_ignore_t)+0x1b4c) [0x6a043c]
xtrabackup(dict_load_table(char const*, unsigned long, dict_err_ignore_t)+0xea5) [0x6a1425]
xtrabackup(dict_load_foreigns(char const*, char const**, bool, bool, dict_err_ignore_t)+0x1b4c) [0x6a043c]
xtrabackup(dict_load_table(char const*, unsigned long, dict_err_ignore_t)+0xea5) [0x6a1425]
xtrabackup(dict_load_table_on_id(unsigned long, dict_err_ignore_t)+0x4ff) [0x6a1fef]
xtrabackup(dict_table_open_on_id(unsigned long, unsigned long, dict_table_op_t)+0xf8) [0x726e48]
xtrabackup(row_purge_step(que_thr_t*)+0x19f) [0x93e46f]
xtrabackup(que_run_threads(que_thr_t*)+0x530) [0x71da90]
xtrabackup(trx_purge(unsigned long, unsigned long, bool)+0x97e) [0x6aea9e]
xtrabackup(srv_purge_coordinator_thread+0x53e) [0x6337ee]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x80a4) [0x7fe0769180a4]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7fe074f3a04d]
Hi,
I'm not really totally sure but does this stack trace is related to the above bug please ? :
xtrabackup version 2.2.10 based on MySQL server 5.6.22 Linux (x86_64) (revision id: ) logfile. will try to find. logfile' . will retry. (2529057519583) data_home_ dir = ./ data_file_ path = ibdata1: 10M:autoextend log_group_ home_dir = ./ log_files_ in_group = 1 log_file_ size = 2981888 data_home_ dir = ./ data_file_ path = ibdata1: 10M:autoextend log_group_ home_dir = ./ log_files_ in_group = 1 log_file_ size = 2981888
xtrabackup: cd to /data/mysql
xtrabackup: This target seems to be not prepared yet.
2015-04-10 18:02:13 7fe076d33740 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
xtrabackup: Warning: cannot open ./xtrabackup_
xtrabackup: 'ib_logfile0' seems to be 'xtrabackup_
xtrabackup: xtrabackup_logfile detected: size=2981888, start_lsn=
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: Starting InnoDB instance for recovery.
xtrabackup: Using 104857600 bytes for buffer pool (set by --use-memory parameter)
InnoDB: Using atomics to ref count buffer pool pages
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Memory barrier is not used
InnoDB: Compressed tables use zlib 1.2.7
InnoDB: Using CPU crc32 instructions
InnoDB: Initializing buffer pool, size = 100.0M
InnoDB: Completed initialization of buffer pool
InnoDB: Highest supported file format is Barracuda.
InnoDB: The log sequence numbers 2387850439738 and 2387850439738 in ibdata files do not match the log sequence number 2529057519583 in the ib_logfiles!
InnoDB: Database was not shutdown normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages
InnoDB: from the doublewrite buffer...
InnoDB: 128 rollback segment(s) are active.
InnoDB: Waiting for purge to start
16:02:13 UTC - xtrabackup got signal 11 ;
This could be because you hit a bug or data is corrupted.
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.
Thread pointer: 0x0 my_print_ stacktrace+ 0x2b) [0x8ed1db] handle_ fatal_signal+ 0x252) [0x799202] 64-linux- gnu/libpthread. so.0(+0xf8d0) [0x7fe07691f8d0] THD::raise_ condition( unsigned int, char const*, Sql_condition: :enum_warning_ level, char const*)+0x22) [0x7d3f12] push_warning_ printf( THD*, Sql_condition: :enum_warning_ level, unsigned int, char const*, ...)+0xb9) [0x886359] ib_warn_ row_too_ big(dict_ table_t const*)+0x7f) [0x69bc6f] dict_index_ add_to_ cache(dict_ table_t* , dict_index_t*, unsigned long, unsigned long)+0x94b) [0x72854b] dict_load_ table(char const*, unsigned long, dict_err_ ignore_ t)+0xb7e) [0x6a10fe] dict_load_ foreigns( char const*, char const**, bool, bool, dict_err_ ignore_ t)+0x1b4c) [0x6a043c] dict_load_ table(char const*, unsigned long, dict_err_ ignore_ t)+0xea5) [0x6a1425] dict_load_ foreigns( char const*, char const**, bool, bool, dict_err_ ignore_ t)+0x1b4c) [0x6a043c] dict_load_ table(char const*, unsigned long, dict_err_ ignore_ t)+0xea5) [0x6a1425] dict_load_ foreigns( char const*, char const**, bool, bool, dict_err_ ignore_ t)+0x1b4c) [0x6a043c] dict_load_ table(char const*, unsigned long, dict_err_ ignore_ t)+0xea5) [0x6a1425] dict_load_ table_on_ id(unsigned long, dict_err_ ignore_ t)+0x4ff) [0x6a1fef] dict_table_ open_on_ id(unsigned long, unsigned long, dict_table_ op_t)+0xf8) [0x726e48] row_purge_ step(que_ thr_t*) +0x19f) [0x93e46f] que_run_ threads( que_thr_ t*)+0x530) [0x71da90] trx_purge( unsigned long, unsigned long, bool)+0x97e) [0x6aea9e] srv_purge_ coordinator_ thread+ 0x53e) [0x6337ee] 64-linux- gnu/libpthread. so.0(+0x80a4) [0x7fe0769180a4] 64-linux- gnu/libc. so.6(clone+ 0x6d) [0x7fe074f3a04d]
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 0x10000
InnoDB: 5.6.22 started; log sequence number 2529057519583
xtrabackup(
xtrabackup(
/lib/x86_
xtrabackup(
xtrabackup(
xtrabackup(
xtrabackup(
xtrabackup() [0x6a366b]
xtrabackup(
xtrabackup(
xtrabackup(
xtrabackup(
xtrabackup(
xtrabackup(
xtrabackup(
xtrabackup(
xtrabackup(
xtrabackup(
xtrabackup(
xtrabackup(
xtrabackup(
/lib/x86_
/lib/x86_
Please report a bug at https:/ /bugs.launchpad .net/percona- xtrabackup
Regards,
Laurent