xtrabackup got signal 11 if you will decrypt+decompress+prepare backup twice
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-
Prepared as:
Trying to decrypt backup
Running decrypt command -> /usr/bin/xtrabackup --decrypt=AES256 --encrypt-
0120 16:02:42 completed OK!
Decrypted!
Trying to decompress backup
Running decompress command -> /usr/bin/xtrabackup --decompress=TRUE --target-
0120 16:02:43 completed OK!
Decompressed
Running prepare command -> /usr/bin/xtrabackup --prepare --target-
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-
0120 16:03:02 completed OK!
Decrypted!
Trying to decompress backup
Running decompress command -> /usr/bin/xtrabackup --decompress=TRUE --target-
0120 16:03:03 completed OK!
Decompressed
Running prepare command -> /usr/bin/xtrabackup --prepare --target-
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_
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_
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: PUNCH HOLE support available
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Uses event mutexes
InnoDB: GCC builtin __atomic_
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/
/usr/bin/
/lib64/
/usr/bin/
/usr/bin/
/usr/bin/
/usr/bin/
/lib64/
/lib64/
Percona now uses JIRA for bug reports so this bug report is migrated to: https:/ /jira.percona. com/browse/ PXB-782