Failed to take full backup -> CORRUPT LOG RECORD FOUND

Bug #1604367 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
Triaged
Low
Sergei Glushchenko

Bug Description

Testing same scenario -> https://bugs.launchpad.net/percona-xtrabackup/+bug/1582130
With -> https://launchpad.net/percona-xtrabackup/+milestone/2.4.4

1. Run python script (altering master key) -> leave running
2. alter table sbtest1 compression='zlib';
3. /usr/local/xtrabackup/bin/xtrabackup --defaults-file=/home/sh/sandboxes/msb_5_7_11/my.sandbox.cnf --backup --datadir=/home/sh/sandboxes/msb_5_7_11/data/ --target-dir=/home/backup_dir/full/ --user=msandbox --password=msandbox --no-version-check --keyring-file-data=/home/sh/sandboxes/msb_5_7_11/tmp/keyring --server-id=0

Using server version 5.7.11-4
/usr/local/xtrabackup/bin/xtrabackup version 2.4.3 based on MySQL server 5.7.13 Linux (x86_64) (revision id: 2d5c4c0)
xtrabackup: uses posix_fadvise().
xtrabackup: cd to /home/sh/sandboxes/msb_5_7_11/data/
xtrabackup: open files limit requested 0, set to 1024
xtrabackup: using the following InnoDB configuration:
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 = 2
xtrabackup: innodb_log_file_size = 50331648
InnoDB: Number of pools: 1
InnoDB: Encryption information in the redo log of space 31 is invalid
InnoDB: ############### CORRUPT LOG RECORD FOUND ##################
InnoDB: Log record type 30, page 31:0. Log parsing proceeded successfully up to 186608742. Previous log record type 30, is multi 0 Recv offset 90, prev 0
InnoDB: Hex dump starting 0 bytes before and ending 100 bytes after the corrupted record:
 len 190; hex 9e1f00289600536c43410000ab5d00000000f8cc7905c9d0145f5a7d1d5dff079f024fbc70e3a7223c8a7c76193f92e92dd03eba2ef29102b9eaa952426c121f42c09a51c1223509b83eae7afe65e986094512c2841b000000009e1f00289600536c43410000ab5e00000000e0d8cd4e82d6655b978a0a4be19597bfc98a1127507c8bd9a49ddf425a8404f73fab8624387ff1f5ffc02457fef65de713298c9f4b0c25d0bcade991c4fb269f12c2841b000000009e1f00289600536c4341; asc ( SlCA ] y _Z} ] O p "< |v ? - > . RBl B Q "5 > z e E ( SlCA ^ N e[ K 'P| BZ ? $8 $W ] ) K % & ( SlCA;
InnoDB: Set innodb_force_recovery to ignore this error.
160719 15:31:07 >> log scanned up to (186609243)
xtrabackup: Generating a list of tablespaces

Changed in percona-xtrabackup:
importance: High → Medium
Revision history for this message
Sergei Glushchenko (sergei.glushchenko) wrote :

Setting to low because bug is only reproducible in 5.7.11

Changed in percona-xtrabackup:
importance: Medium → Low
Revision history for this message
Sergei Glushchenko (sergei.glushchenko) wrote :
Changed in percona-xtrabackup:
status: Confirmed → Fix Committed
assignee: nobody → Sergei Glushchenko (sergei.glushchenko)
milestone: none → 2.4.4
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-942

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.