percona-discussion team mailing list archive

[Yasufumi Kinoshita <yasufumi.kinoshita@xxxxxxxxxxx>]

** Changed in: percona-xtrabackup
       Status: New => Fix Committed

** Changed in: percona-xtrabackup
   Importance: Undecided => Medium
       Status: Fix Committed => Fix Released

-- 
failed --apply-log at innobase_mysql_cmp() is called
https://bugs.launchpad.net/bugs/338568
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:
Sometimes I am getting

./innobackup-1.5.1 --apply-log /var/lib/mysql/backup/2009-03-05_23-27-27/                                    

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)
'

090305 23:43:11  innobackup: Starting ibbackup with command: ./xtrabackup --prepare --target-dir=/var/lib/mysql/backup/2009-03-05_23-27-27

./xtrabackup  Ver alpha-0.2 for 5.0.77 unknown-linux-gnu (x86_64)
xtrabackup_logfile detected: size=2392064, start_lsn=(53 2031047667)
InnoDB: Log scan progressed past the checkpoint lsn 53 2031047667
090305 23:43:11  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 2033428951
090305 23:43:13  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: In a MySQL replication slave the last master binlog file
InnoDB: position 0 61526249, file name mysql-bin.000428
InnoDB: Last MySQL binlog file position 0 2686, file name /var/log/mysql/mysql-bin.000019
090305 23:43:19  InnoDB: Started; log sequence number 53 2033428951

[notice (again)]
  If you use binary log and don't use any hack of group commit,
  the binary log position seems to be:
InnoDB: Last MySQL binlog file position 0 2686, file name /var/log/mysql/mysql-bin.000019

090305 23:43:19  InnoDB: Starting shutdown...
innobase_mysql_cmp() is called
innobackup: Error: 
innobackup: ibbackup failed at ./innobackup-1.5.1 line 402.



Check

090305 23:43:19  InnoDB: Starting shutdown...
innobase_mysql_cmp() is called
innobackup: Error: 
innobackup: ibbackup failed at ./innobackup-1.5.1 line 402.