InnoDB: Probable data corruption on page 158
Bug #1190042 reported by
George Ormond Lorch III
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
This may be the came cause as https:/
While running XtraBackup 2.1 (revno 609) against Percona Server 5.6 (revno 382) using PTB and RQG as the load mechanism, preparing an incremental fails with InnoDB: Probable data corruption on page 158.
I was running into this consistently on a local test machine, with spinning media. Always page 158. To rule out hardware, I ran this same test on an HP Cloud Instance to the exact same effect.
( PATH=/mnt/ bin/ps- 5.6/bin: /mnt/bin/ ps-5.6/ libexec: /mnt/bin/ xb-2.1- xtradb56: /usr/local/ sbin:/usr/ local/bin: /sbin:/ bin:/usr/ sbin:/usr/ bin:/root/ bin; innobackupex --defaults- file=/mnt/ test/var/ test-0/ mysql.1/ my.cnf --apply-log --redo-only --incremental- dir=/mnt/ test/var/ test-0/ restore- 0.3 /mnt/test/ var/test- 0/restore- working )
Log innobacupex output attached here in restore-0.3.log