← Back to team overview

percona-discussion team mailing list archive

[Bug 339013] Re: apply-log fails with error log seq number is in future

 

Here is log from backup

./innobackup-1.5.1 /var/lib/mysql/backup/

InnoDB Backup Utility v1.5.1-xtrabackup; Copyright 2003, 2009 Innobase Oy.
All Rights Reserved.

This software is published under
the GNU GENERAL PUBLIC LICENSE Version 2, June 1991.

IMPORTANT: Please check that the backup run completes successfully.
           At the end of a successful backup run innobackup
           prints "innobackup completed OK!".

innobackup: Using mysql  Ver 14.12 Distrib 5.0.67, for redhat-linux-gnu (x86_64) using readline 5.1
innobackup: Using mysql server version 5.0.67-percona-b7-log

innobackup:: Warning: Ignored unrecognized line 1 in options : './xtrabackup  Ver alpha-0.2 for 5.0.77 unknown-linux-gnu (x86_64)
'
innobackup: Created backup directory /var/lib/mysql/backup/2009-03-06_17-06-17
090306 17:06:17  innobackup: Starting mysql with options: --unbuffered
090306 17:06:17  innobackup: Connected to database with mysql child process (pid=3084)
090306 17:06:21  innobackup: Connection to database server closed

090306 17:06:21  innobackup: Starting ibbackup with command: ./xtrabackup --backup --suspend-at-end --target-dir=/var/lib/mysql/backup/2009-03-06_17-06-17
innobackup: Waiting for ibbackup (pid=3094) to suspend
innobackup: Suspend file '/var/lib/mysql/backup/2009-03-06_17-06-17/xtrabackup_suspended'

./xtrabackup  Ver alpha-0.2 for 5.0.77 unknown-linux-gnu (x86_64)
>> log scanned up to (53 2204070829)
Copying ./ibdata1 
     to /var/lib/mysql/backup/2009-03-06_17-06-17/ibdata1
        ...done

..........

innobackup: Backing up files '/var/lib/mysql/st/*.{frm,MYD,MYI,MRG,TRG,TRN,opt}' (159 files)
>> log scanned up to (53 2207846582)
>> log scanned up to (53 2207846582)
>> log scanned up to (53 2207846582)
>> log scanned up to (53 2207846582)
090306 17:21:50  innobackup: Finished backing up .frm, .MRG, .MYD, .MYI, .TRG, .TRN, and .opt files

innobackup: Resuming ibbackup

Stopping log copying thread.>> log scanned up to (53 2207846582)

Transaction log of lsn (53 2203680185) to (53 2207846582) was copied.
090306 17:21:55  innobackup: All tables unlocked
090306 17:21:55  innobackup: Connection to database server closed

innobackup: Backup created in directory '/var/lib/mysql/backup/2009-03-06_17-06-17'
innobackup: MySQL binlog position: filename 'mysql-bin.000020', position 530    
090306 17:21:55  innobackup: innobackup completed OK!

-- 
apply-log fails with error log seq number is in future
https://bugs.launchpad.net/bugs/339013
You received this bug notification because you are a member of Percona
developers, which is the registrant for Percona-XtraBackup.

Status in Open source backup tool for InnoDB and XtraDB: New

Bug description:
./innobackup-1.5.1 --apply-log /var/lib/mysql/backup/2009-03-06_17-06-17/                                    

InnoDB Backup Utility v1.5.1-xtrabackup; Copyright 2003, 2009 Innobase Oy.
All Rights Reserved.

This software is published under
the GNU GENERAL PUBLIC LICENSE Version 2, June 1991.

IMPORTANT: Please check that the apply-log run completes successfully.
           At the end of a successful apply-log run innobackup
           prints "innobackup completed OK!".


innobackup:: Warning: Ignored unrecognized line 1 in options : './xtrabackup  Ver alpha-0.2 for 5.0.77 unknown-linux-gnu (x86_64)
'

090306 19:51:58  innobackup: Starting ibbackup with command: ./xtrabackup --prepare --target-dir=/var/lib/mysql/backup/2009-03-06_17-06-17

./xtrabackup  Ver alpha-0.2 for 5.0.77 unknown-linux-gnu (x86_64)
xtrabackup_logfile detected: size=4177920, start_lsn=(53 2203680185)
InnoDB: Log scan progressed past the checkpoint lsn 53 2203680185
090306 19:51:58  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 53 2206675456
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 1 row operations to undo
InnoDB: Trx id counter is 0 457053440
090306 19:52:00  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 0 1 2 3 4 090306 19:52:00  InnoDB: Error: page 5698 log sequence number 53 2206837124
InnoDB: is in the future! Current system log sequence number 53 2206675233.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.
090306 19:52:00  InnoDB: Error: page 5730 log sequence number 53 2206720672
InnoDB: is in the future! Current system log sequence number 53 2206675233.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: for more information.



References