Xtrabackup Page directory corruption error while apply-log

MySQL & MariaDB Percona XtraBackup
1

Version:

Xtrabacku 1.6
mysql 5.5.13
Linux 2.6.18-238.5.1.el5 #1 SMP Mon Feb 21 05:52:39 EST 2011 x86_64

Issue:

/mysql/xtrabackup/bin/innobackupex-1.5.1 --apply-log --ibbackup=/mysql/db01/xtrabackup-1.6/bin/xtrabackup_55 --defaults-file=/usr/local/mysql/data/my.cnf /usr/local/mysql/data/

InnoDB: Apply batch completed
InnoDB: Last MySQL binlog file position 0 40743994, file name /mysql/binlogs/s2r2-log-bin.001072
InnoDB: Page directory corruption: infimum not pointed to
110927 13:31:50 InnoDB: Page dump in ascii and hex (16384 bytes):

InnoDB: End of page dump
110927 13:31:50 InnoDB: Page checksum 2207762029 (32bit_calc: 858448952), prior-to-4.0.14-form checksum 3632172825
InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 437
InnoDB: Page lsn 437 177712030, low 4 bytes of lsn at page end 177712030
InnoDB: Page number (if stored to page already) 98306,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be an update undo log page
InnoDB: Page directory corruption: supremum not pointed to
110927 13:31:50 InnoDB: Page dump in ascii and hex (16384 bytes):

InnoDB: End of page dump
110927 13:31:50 InnoDB: Page checksum 2207762029 (32bit_calc: 858448952), prior-to-4.0.14-form checksum 3632172825
InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 437
InnoDB: Page lsn 437 177712030, low 4 bytes of lsn at page end 177712030
InnoDB: Page number (if stored to page already) 98306,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be an update undo log page
innobackupex-1.5.1: Error:
innobackupex-1.5.1: ibbackup failed at /mysql/xtrabackup/bin/innobackupex-1.5.1 line 336.

Anyone having this issue?

Is there any option which can restore to the last valid LSN or before the corrupt log position?

I was able to start the db by doing following:

/mysql/xtrabackup/bin/innobackupex-1.5.1 --apply-log --redo-only --ibbackup=/mysql/db01/xtrabackup-1.6/bin/xtrabackup_55 --defaults-file=/usr/local/mysql/data/my.cnf /usr/local/mysql/data/

followed by the following:

/mysql/xtrabackup/bin/innobackupex-1.5.1 --apply-log --ibbackup=/mysql/db01/xtrabackup-1.6/bin/xtrabackup_55 --defaults-file=/usr/local/mysql/data/my.cnf /usr/local/mysql/data/

Any issue in doing the above? It does give me the page dump but on the same hand i was able to get my all binlog files and i was able to start the db.

I will highly appreciate if anyone can assist me in this issue.

Best Regards,

2

I’ve upgraded the Xtrabackup to xtrabackup-1.6.3 but still this problem exists. Please see below for errors

111010 10:37:41 InnoDB: Starting an apply batch of log records to the database…
InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
InnoDB: Last MySQL binlog file position 0 43014298, file name /mysql/binlogs/s4r2-log-bin.001377
InnoDB: Page directory corruption: infimum not pointed to
111010 10:38:02 InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex
InnoDB: End of page dump
111010 10:38:03 InnoDB: Page checksum 1850373594 (32bit_calc: 3127788176), prior-to-4.0.14-form checksum 3710364808
InnoDB: stored checksum 1850373594, prior-to-4.0.14-form stored checksum 3710364808
InnoDB: Page lsn 551 1666729731, low 4 bytes of lsn at page end 1666729731
InnoDB: Page number (if stored to page already) 33216,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be an update undo log page
InnoDB: Page directory corruption: supremum not pointed to
111010 10:38:03 InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex
InnoDB: End of page dump
111010 10:38:03 InnoDB: Page checksum 1850373594 (32bit_calc: 3127788176), prior-to-4.0.14-form checksum 3710364808
InnoDB: stored checksum 1850373594, prior-to-4.0.14-form stored checksum 3710364808
InnoDB: Page lsn 551 1666729731, low 4 bytes of lsn at page end 1666729731
InnoDB: Page number (if stored to page already) 33216,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be an update undo log page
InnoDB: Next record offset is nonsensical 20795 in record at offset 0
InnoDB: rec address 0x2aaaacb64000, space id 0, page 33216
111010 10:38:03 InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex
InnoDB: End of page dump
111010 10:38:03 InnoDB: Page checksum 1850373594 (32bit_calc: 3127788176), prior-to-4.0.14-form checksum 3710364808
InnoDB: stored checksum 1850373594, prior-to-4.0.14-form stored checksum 3710364808
InnoDB: Page lsn 551 1666729731, low 4 bytes of lsn at page end 1666729731
InnoDB: Page number (if stored to page already) 33216,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be an update undo log page
111010 10:38:03 InnoDB: Assertion failure in thread 47198056535504 in file /home/buildbot/slaves/percona-server-51-12/TGZ_CentOS_5_x86_ 64/work/xtrabackup-1.6.3/Percona-Server-5.5/storage/innobase /include/page0page.ic line 718
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recove ry.html
InnoDB: about forcing recovery.
/mysql/xtrabackup/bin/xtrabackup_55 version 1.6.3 for Percona Server 5.5.9 Linux (x86_64) (revision id: undefined)
xtrabackup: xtrabackup_logfile detected: size=7183040512, start_lsn=(2361809722957)
innobackupex-1.5.1: Error:
innobackupex-1.5.1: ibbackup failed at /mysql/xtrabackup/bin/innobackupex-1.5.1 line 336.

Any help would be highly appreciable. This is happening on the last step of restore and i’m not able to find out any way to bypass it or do the recovery till the last good lsn.

Regards,