xtrabackup got signal 11 if you will decrypt+decompress+prepare backup twice

Bug #1658073 reported by Shahriyar Rzayev
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraBackup moved to https://jira.percona.com/projects/PXB
Status tracked in 2.4
2.4
Confirmed
Medium
Unassigned

Bug Description

Hi dear all,

Took the backup as:

/usr/bin/xtrabackup --defaults-file=/etc/my.cnf --user=root --password='Baku12345#' --target-dir=/home/backup_dir/full/2017-01-20_16-02-12 --backup --host=127.0.0.1 --port=3306 --compress=quicklz --compress-chunk-size=65536 --compress-threads=4 --encrypt=AES256 --encrypt-key='VVTBwgM4UhwkTTV98fhuj+D1zyWoA89K' --encrypt-threads=4 --encrypt-chunk-size=65536

Prepared as:

Trying to decrypt backup
Running decrypt command -> /usr/bin/xtrabackup --decrypt=AES256 --encrypt-key='VVTBwgM4UhwkTTV98fhuj+D1zyWoA89K' --target-dir=/home/backup_dir/full/2017-01-20_16-02-12
0120 16:02:42 completed OK!
Decrypted!
Trying to decompress backup
Running decompress command -> /usr/bin/xtrabackup --decompress=TRUE --target-dir=/home/backup_dir/full/2017-01-20_16-02-12
0120 16:02:43 completed OK!
Decompressed
Running prepare command -> /usr/bin/xtrabackup --prepare --target-dir=/home/backup_dir/full/2017-01-20_16-02-12
0120 16:02:46 completed OK!

Then forgot about if I have prepared or not previously, tried again:

Trying to decrypt backup
Running decrypt command -> /usr/bin/xtrabackup --decrypt=AES256 --encrypt-key='VVTBwgM4UhwkTTV98fhuj+D1zyWoA89K' --target-dir=/home/backup_dir/full/2017-01-20_16-02-12
0120 16:03:02 completed OK!
Decrypted!
Trying to decompress backup
Running decompress command -> /usr/bin/xtrabackup --decompress=TRUE --target-dir=/home/backup_dir/full/2017-01-20_16-02-12
0120 16:03:03 completed OK!
Decompressed
Running prepare command -> /usr/bin/xtrabackup --prepare --target-dir=/home/backup_dir/full/2017-01-20_16-02-12
FULL BACKUP PREPARE FAILED!
/usr/bin/xtrabackup version 2.4.5 based on MySQL server 5.7.13 Linux (x86_64) (revision id: e41c0be)
xtrabackup: cd to /home/backup_dir/full/2017-01-20_16-02-12
xtrabackup: This target seems to be not prepared yet.
InnoDB: Number of pools: 1
xtrabackup: xtrabackup_logfile detected: size=8388608, start_lsn=(2550340)
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup: innodb_data_home_dir = .
xtrabackup: innodb_data_file_path = ibdata1:12M:autoextend
xtrabackup: innodb_log_group_home_dir = .
xtrabackup: innodb_log_files_in_group = 1
xtrabackup: innodb_log_file_size = 8388608
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup: innodb_data_home_dir = .
xtrabackup: innodb_data_file_path = ibdata1:12M:autoextend
xtrabackup: innodb_log_group_home_dir = .
xtrabackup: innodb_log_files_in_group = 1
xtrabackup: innodb_log_file_size = 8388608
xtrabackup: Starting InnoDB instance for recovery.
xtrabackup: Using 104857600 bytes for buffer pool (set by --use-memory parameter)
InnoDB: PUNCH HOLE support available
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Uses event mutexes
InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
InnoDB: Compressed tables use zlib 1.2.7
InnoDB: Number of pools: 1
InnoDB: Using CPU crc32 instructions
InnoDB: Initializing buffer pool, total size = 100M, instances = 1, chunk size = 100M
InnoDB: Completed initialization of buffer pool
InnoDB: page_cleaner coordinator priority: -20
InnoDB: Log file ./ib_logfile1 is of different size 50331648 bytes than other log files 8388608 bytes!
InnoDB: Plugin initialization aborted with error Generic error
12:03:03 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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might 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
/usr/bin/xtrabackup(my_print_stacktrace+0x2c)[0xceaf1c]
/usr/bin/xtrabackup(handle_fatal_signal+0x262)[0x9ca752]
/lib64/libpthread.so.0(+0xf370)[0x7f0dcbd9a370]
/usr/bin/xtrabackup(_Z19rw_lock_x_lock_funcP9rw_lock_tmPKcm+0x50)[0x7afbd0]
/usr/bin/xtrabackup(_Z15trx_purge_statev+0x2a)[0x89fa8a]
/usr/bin/xtrabackup(_Z26srv_get_active_thread_typev+0xc4)[0x88b644]
/usr/bin/xtrabackup(buf_flush_page_cleaner_coordinator+0x725)[0x878d65]
/lib64/libpthread.so.0(+0x7dc5)[0x7f0dcbd92dc5]
/lib64/libc.so.6(clone+0x6d)[0x7f0dc9b5b73d]

Tags: qa
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-782

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.