percona-discussion team mailing list archive

[MarkD <mark.davis@xxxxxxxxx>]

HI Vadim,

just got the latest revno. 34 from launchpad. Began from scratch
(extract, patch, build).

# /home/md/xtrabackup --backup
./xtrabackup  Ver beta-0.4 for 5.1.32 unknown-linux-gnu (x86_64)
>> log scanned up to (25 733862973)                             
Copying //mysql/data/ibdata1                                    
     to /mysql/backup/ibdata1                                   
>> log scanned up to (25 734293011)                             
>> log scanned up to (25 734619380)                             
        ...done                                                 
>> log scanned up to (25 734971958)           
...
The latest check point (for incremental): '25:579639574'        
>> log scanned up to (25 769313172)                             
Stopping log copying thread.                                    
Transaction log of lsn (25 543693125) to (25 769313172) was copied.

Now the --prepare directly fails at start:

# ./xtrabackup --prepare
./xtrabackup  Ver beta-0.4 for 5.1.32 unknown-linux-gnu (x86_64)
xtrabackup: This target seems to be not prepared yet.           
xtrabackup_logfile detected: size=225624064, start_lsn=(25 543693125)
xtrabackup: Starting InnoDB instance for recovery.                   
xtrabackup: Using 104857600 bytes for buffer pool (set by --use-memory parameter)
090403  9:48:58  InnoDB: Operating system error number 2 in a file operation.    
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
InnoDB: File name .//mysql/data/ibdata1
InnoDB: File operation call: 'create'.
InnoDB: Cannot continue operation.

My innodb/xtrabackup config:

innodb_data_file_path = /mysql/data/ibdata1:128M:autoextend
innodb_file_per_table
innodb_log_group_home_dir       = /mysql/logs
innodb_buffer_pool_size         = 4096M             
innodb_additional_mem_pool_size = 32M
innodb_log_file_size            = 128M
innodb_log_files_in_group       = 2
innodb_log_buffer_size          = 16M
innodb_flush_log_at_trx_commit  = 2
innodb_lock_wait_timeout        = 50
innodb_thread_concurrency       = 0

[xtrabackup]
target_dir = /mysql/backup

-- 
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: Fix Released

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.