xtrabackup --prepare to create logfile fails: innodb_init(): Error occured.

Bug #680927 reported by Kenny Gryp
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraBackup moved to https://jira.percona.com/projects/PXB
Fix Released
High
Alexey Kopytov

Bug Description

If you set the innodb_doublewrite_file option, xtrabackup fails to --prepare the 2nd time:

MySQL version: 5.1.51-rel11.5-log
XtraBackup version: Ver 1.4 Rev 193 for 5.1.47 unknown-linux-gnu (x86_64)

xtrabackup Ver 1.4 Rev 193 for 5.1.47 unknown-linux-gnu (x86_64)
xtrabackup: cd to /home/gryp/xtrabackup/tracx/2010-11-24_14-11-49/
xtrabackup: This target seems to be already prepared.
xtrabackup: notice: xtrabackup_logfile was already used to '--prepare'.
xtrabackup: Temporary instance for recovery is set as followings.
xtrabackup: innodb_data_home_dir = ./
xtrabackup: innodb_data_file_path = ibdata1:10M:autoextend
xtrabackup: innodb_log_group_home_dir = ./
xtrabackup: innodb_log_files_in_group = 2
xtrabackup: innodb_log_file_size = 5242880
xtrabackup: Starting InnoDB instance for recovery.
xtrabackup: Using 104857600 bytes for buffer pool (set by --use-memory parameter)
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.3
InnoDB: Warning: innodb_file_io_threads is deprecated. Please use innodb_read_io_threads and innodb_write_io_threads instead
InnoDB: Notice: innodb_doublewrite_file is specified.
InnoDB: This is for expert only. Don't use if you don't understand what is it 'WELL'.
InnoDB: ### Don't specify older file than the last checkpoint ###
InnoDB: otherwise the older doublewrite buffer will break your data during recovery!
101124 14:14:49 InnoDB: Log file ./ib_logfile0 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait...
101124 14:14:49 InnoDB: Log file ./ib_logfile1 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile1 size to 5 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Cannot initialize created log files because
InnoDB: data files were not in sync with each other
InnoDB: or the data files are corrupt.
xtrabackup: innodb_init(): Error occured.

See attachment for more output.

Related branches

Revision history for this message
Kenny Gryp (gryp) wrote :
Percona (percona-team)
Changed in percona-xtrabackup:
assignee: nobody → Alexey Kopytov (akopytov)
milestone: none → 1.6
importance: Undecided → High
Changed in percona-xtrabackup:
status: New → In Progress
Revision history for this message
Alexey Kopytov (akopytov) wrote :

Not repeatable when xtrabackup is built against the latest changes in lp:percona-server. Most likely the problem was fixed by the following changeset: http://bazaar.launchpad.net/~percona-dev/percona-server/release-5.1.53/revision/168

Changed in percona-xtrabackup:
status: In Progress → Fix Committed
Changed in percona-xtrabackup:
status: Fix Committed → Fix Released
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-291

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.