Percona XtraBackup moved to https://jira.percona.com/projects/PXB

  1. Series 2.1
  2. Bug #1155189
  3. Comment #2

Comment 2 for bug 1155189

Revision history for this message
Ovais Tariq (ovais-tariq) wrote : Re: Streaming partial backup when extracted throws the error xb_stream_read_chunk(): wrong chunk magic at offset 0x1b3990e

The output from preparing the uncompressed archive that xbstream reported an error on:

[root@centos6_01 backup_test]# echo "innodb_file_per_table=1" >> uncompress/backup-my.cnf
[root@centos6_01 backup_test]# innobackupex --apply-log --export uncompress/

InnoDB Backup Utility v1.5.1-xtrabackup; Copyright 2003, 2009 Innobase Oy
and Percona Ireland Ltd 2009-2012. All Rights Reserved.

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

option_ibbackup_binary is autodetect, trying to connect to MySQL
Connected to MySQL with pid 6286
130314 11:31:55 innobackupex: Connection to database server closed
Connected successfully
130314 11:31:55 innobackupex: Starting mysql with options: --unbuffered --
130314 11:31:55 innobackupex: Connected to database with mysql child process (pid=6290)
130314 11:32:01 innobackupex: Connection to database server closed
IMPORTANT: Please check that the apply-log run completes successfully.
           At the end of a successful apply-log run innobackupex
           prints "completed OK!".

130314 11:32:01 innobackupex: Starting ibbackup with command: xtrabackup_55 --defaults-file="/root/backup_test/uncompress/backup-my.cnf" --defaults-group="mysqld" --prepare --target-dir=/root/backup_test/uncompress --export

xtrabackup_55 version 2.0.5 for Percona Server 5.5.16 Linux (x86_64) (revision id: 499)
xtrabackup: cd to /root/backup_test/uncompress
xtrabackup: This target seems to be not prepared yet.
xtrabackup: xtrabackup_logfile detected: size=2097152, start_lsn=(23311379)
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 = 1
xtrabackup: innodb_log_file_size = 2097152
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 = 1
xtrabackup: innodb_log_file_size = 2097152
xtrabackup: Starting InnoDB instance for recovery.
xtrabackup: Using 104857600 bytes for buffer pool (set by --use-memory parameter)
130314 11:32:01 InnoDB: The InnoDB memory heap is disabled
130314 11:32:01 InnoDB: Mutexes and rw_locks use GCC atomic builtins
130314 11:32:01 InnoDB: Compressed tables use zlib 1.2.3
130314 11:32:01 InnoDB: Initializing buffer pool, size = 100.0M
130314 11:32:01 InnoDB: Completed initialization of buffer pool
130314 11:32:01 InnoDB: highest supported file format is Barracuda.
130314 11:32:02 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.
130314 11:32:02 InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file './percona/deadlocks.ibd'!
InnoDB: It will be removed from data dictionary.
130314 11:32:03 InnoDB: Waiting for the background threads to start
130314 11:32:04 Percona XtraDB (http://www.percona.com) 1.1.8-20.1 started; log sequence number 23311379
xtrabackup: export option is specified.
xtrabackup: export metadata of table 'test/t2' to file `./test/t2.exp` (1 indexes)
xtrabackup: name=PRIMARY, id.low=52, page=3
xtrabackup: export metadata of table 'test/t3' to file `./test/t3.exp` (1 indexes)
xtrabackup: name=PRIMARY, id.low=53, page=3
xtrabackup: export metadata of table 'test/test_export' to file `./test/test_export.exp` (1 indexes)
xtrabackup: name=PRIMARY, id.low=55, page=3

[notice (again)]
  If you use binary log and don't use any hack of group commit,
  the binary log position seems to be:

xtrabackup: starting shutdown with innodb_fast_shutdown = 0
130314 11:32:05 InnoDB: Starting shutdown...
130314 11:32:08 InnoDB: Shutdown completed; log sequence number 23313262

130314 11:32:08 innobackupex: Restarting xtrabackup with command: xtrabackup_55 --defaults-file="/root/backup_test/uncompress/backup-my.cnf" --defaults-group="mysqld" --prepare --target-dir=/root/backup_test/uncompress --export
for creating ib_logfile*

xtrabackup_55 version 2.0.5 for Percona Server 5.5.16 Linux (x86_64) (revision id: 499)
xtrabackup: cd to /root/backup_test/uncompress
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: 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)
130314 11:32:08 InnoDB: The InnoDB memory heap is disabled
130314 11:32:08 InnoDB: Mutexes and rw_locks use GCC atomic builtins
130314 11:32:08 InnoDB: Compressed tables use zlib 1.2.3
130314 11:32:08 InnoDB: Initializing buffer pool, size = 100.0M
130314 11:32:08 InnoDB: Completed initialization of buffer pool
130314 11:32:08 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...
130314 11:32:08 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...
130314 11:32:09 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
130314 11:32:09 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
130314 11:32:10 InnoDB: Waiting for the background threads to start
130314 11:32:11 Percona XtraDB (http://www.percona.com) 1.1.8-20.1 started; log sequence number 23313420
xtrabackup: export option is specified.
xtrabackup: export metadata of table 'test/t2' to file `./test/t2.exp` (1 indexes)
xtrabackup: name=PRIMARY, id.low=52, page=3
xtrabackup: export metadata of table 'test/t3' to file `./test/t3.exp` (1 indexes)
xtrabackup: name=PRIMARY, id.low=53, page=3
xtrabackup: export metadata of table 'test/test_export' to file `./test/test_export.exp` (1 indexes)
xtrabackup: name=PRIMARY, id.low=55, page=3

[notice (again)]
  If you use binary log and don't use any hack of group commit,
  the binary log position seems to be:

xtrabackup: starting shutdown with innodb_fast_shutdown = 0
130314 11:32:11 InnoDB: Starting shutdown...
130314 11:32:15 InnoDB: Shutdown completed; log sequence number 23313420
130314 11:32:15 innobackupex: completed OK!

See it does not report any error.