InnoDB: Probable data corruption on page 158

Bug #1190042 reported by George Ormond Lorch III
8
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://bugs.launchpad.net/percona-xtrabackup/+bug/1177142 but this is running without changed page tracking and against PS 5.6.

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.

Tags: ptb
Revision history for this message
George Ormond Lorch III (gl-az) wrote :

( 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

Revision history for this message
George Ormond Lorch III (gl-az) wrote :

my.cnf

[client]
port=10000
socket=/mnt/test/var/test-0/mysql.1/mysql.sock
[mysqld]
basedir=/mnt/bin/ps-5.6
datadir=/mnt/test/var/test-0/mysql.1/data
tmpdir=/mnt/test/var/test-0/mysql.1/tmp
port=10000
socket=/mnt/test/var/test-0/mysql.1/mysql.sock
pid-file=/mnt/test/var/test-0/mysql.1/mysql.pid
console
user=root
server-id=1
general-log-file=/mnt/test/var/test-0/mysql.1/query.log
innodb_buffer_pool_size=1G
innodb_file_format=barracuda
innodb_file_per_table=1
innodb_flush_log_at_trx_commit=0
innodb_flush_method=O_DIRECT
innodb_flush_neighbors=0
innodb_log_file_size=512M
innodb_purge_threads=1
innodb_track_changed_pages=0

tags: added: ptb
Revision history for this message
Alexey Kopytov (akopytov) wrote :

Identical failure in MEB: http://bugs.mysql.com/bug.php?id=62587

Revision history for this message
Alexey Kopytov (akopytov) wrote :

Is this repeatable with the current XB trunk (or XB 2.1.4)?

Changed in percona-xtrabackup:
status: New → Incomplete
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-1231

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.