InnoDB: Warning: table 'mysql/innodb_index_stats' in InnoDB data dictionary has unknown flags 50.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MySQL Server |
Unknown
|
Unknown
|
|||
Percona Server moved to https://jira.percona.com/projects/PS |
Invalid
|
Low
|
Unassigned | ||
5.6 |
Invalid
|
Low
|
Unassigned | ||
Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Invalid
|
Undecided
|
Unassigned | ||
2.1 |
Fix Released
|
Low
|
Alexey Kopytov | ||
2.2 |
Invalid
|
Undecided
|
Unassigned |
Bug Description
I'm seeing this message when running XtraBackup, but others have said they see it in the error logs.
https:/
http://
Below are commands I used to reproduce on a new machine, followed by a very lightly spaced out and commented copy of the full console session.
Steps to reproduce on clean machine:
- I used an EC2 instance ( m1.small - Ubuntu Server 13.10 (PV) - ami-7eaecc4e (64-bit) ) -
ubuntu@
root@ip-
root@ip-
root@ip-
root@ip-
root@ip-
[[ did not set root password ]]
root@ip-
root@ip-
root@ip-
root@ip-
root@ip-
[[ no issue so far ]]
root@ip-
root@ip-
root@ip-
root@ip-
root@ip-
root@ip-
root@ip-
root@ip-
root@ip-
root@ip-
root@ip-
root@ip-
root@ip-
...
InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
InnoDB: New log files created, LSN=1650086
InnoDB: Highest supported file format is Barracuda.
InnoDB: 128 rollback segment(s) are active.
InnoDB: Waiting for purge to start
2014-04-04 22:47:56 7f5e32d84700 InnoDB: Warning: table 'mysql/
InnoDB: in InnoDB data dictionary has unknown flags 50.
2014-04-04 22:47:56 7f5e32d84700 InnoDB: Warning: table 'mysql/
InnoDB: in InnoDB data dictionary has unknown flags 50.
InnoDB: 5.6.15 started; log sequence number 1650188
...
-- Issue reached --
-- FULL SESSION BELOW --
login as: ubuntu
Authenticating with public key "foo"
The programs included with the Ubuntu system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/
Ubuntu comes with ABSOLUTELY NO WARRANTY, to the extent permitted by
applicable law.
ubuntu@
root@ip-
Executing: gpg --ignore-
gpg: requesting key CD2EFD2A from hkp server keys.gnupg.net
gpg: key CD2EFD2A: public key "Percona MySQL Development Team <email address hidden>" imported
gpg: Total number processed: 1
gpg: imported: 1
root@ip-
root@ip-
root@ip-
Ign http://
Ign http://
Get:1 http://
Get:2 http://
Get:3 http://
Get:4 http://
Get:5 http://
Ign http://
Get:6 http://
Get:7 http://
Get:8 http://
Get:9 http://
Get:10 http://
Get:11 http://
Get:12 http://
Get:13 http://
Ign http://
Get:14 http://
Ign http://
Get:15 http://
Get:16 http://
Get:17 http://
Get:18 http://
Get:19 http://
Get:20 http://
Get:21 http://
Get:22 http://
Get:23 http://
Ign http://
Ign http://
Ign http://
Ign http://
Ign http://
Ign http://
Ign http://
Ign http://
Ign http://
Ign http://
Fetched 15.0 MB in 18s (810 kB/s)
Reading package lists... Done
root@ip-
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
libaio1 libdbd-mysql-perl libdbi-perl libmysqlclient18 libperconaserve
Suggested packages:
libclone-perl libmldbm-perl libnet-daemon-perl libplrpc-perl libsql-
The following NEW packages will be installed:
libaio1 libdbd-mysql-perl libdbi-perl libmysqlclient18 libperconaserve
xtrabackup
0 upgraded, 10 newly installed, 0 to remove and 34 not upgraded.
Need to get 40.3 MB of archives.
After this operation, 138 MB of additional disk space will be used.
Do you want to continue [Y/n]?
Get:1 http://
Get:2 http://
Get:3 http://
Get:4 http://
Get:5 http://
Get:6 http://
Get:7 http://
Get:8 http://
Get:9 http://
Get:10 http://
Fetched 40.3 MB in 9s (4,334 kB/s)
Preconfiguring packages ...
Selecting previously unselected package libaio1:amd64.
(Reading database ... 53343 files and directories currently installed.)
Unpacking libaio1:amd64 (from .../libaio1_
Selecting previously unselected package percona-
Unpacking percona-
Selecting previously unselected package libdbi-perl.
Unpacking libdbi-perl (from .../libdbi-
Selecting previously unselected package libperconaserve
Unpacking libperconaserve
Selecting previously unselected package percona-
Unpacking percona-
Selecting previously unselected package libmysqlclient18.
Unpacking libmysqlclient18 (from .../libmysqlcli
Selecting previously unselected package libdbd-mysql-perl.
Unpacking libdbd-mysql-perl (from .../libdbd-
Processing triggers for man-db ...
Setting up percona-
Selecting previously unselected package percona-
(Reading database ... 53585 files and directories currently installed.)
Unpacking percona-
Selecting previously unselected package percona-xtrabackup.
Unpacking percona-xtrabackup (from .../percona-
Selecting previously unselected package xtrabackup.
Unpacking xtrabackup (from .../xtrabackup_
Processing triggers for ureadahead ...
Processing triggers for man-db ...
Setting up libaio1:amd64 (0.3.109-4) ...
Setting up libdbi-perl (1.627-1) ...
Setting up libperconaserve
Setting up percona-
Setting up libmysqlclient18 (5.5.35-
Setting up libdbd-mysql-perl (4.023-1) ...
Setting up percona-
* Stopping MySQL (Percona Server) mysqld [ OK ]
* Percona Server is distributed with several useful UDF (User Defined Function) from Percona Toolkit.
* Run the following commands to create these functions:
mysql -e "CREATE FUNCTION fnv1a_64 RETURNS INTEGER SONAME 'libfnv1a_udf.so'"
mysql -e "CREATE FUNCTION fnv_64 RETURNS INTEGER SONAME 'libfnv_udf.so'"
mysql -e "CREATE FUNCTION murmur_hash RETURNS INTEGER SONAME 'libmurmur_udf.so'"
* See http://
* Starting MySQL (Percona Server) database server mysqld [ OK ]
* Checking for corrupt, not cleanly closed and upgrade needing tables.
Setting up percona-xtrabackup (2.1.8-733-1.saucy) ...
Setting up xtrabackup (2.1.3-618-1) ...
Processing triggers for libc-bin ...
Processing triggers for ureadahead ...
[[ did not set root password ]]
root@ip-
root@ip-
root@ip-
root@ip-
InnoDB Backup Utility v1.5.1-xtrabackup; Copyright 2003, 2009 Innobase Oy
and Percona LLC and/or its affiliates 2009-2013. All Rights Reserved.
This software is published under
the GNU GENERAL PUBLIC LICENSE Version 2, June 1991.
Get the latest version of Percona XtraBackup, documentation, and help resources:
http://
140404 22:32:23 innobackupex: Connecting to MySQL server with DSN 'dbi:mysql:
140404 22:32:23 innobackupex: Connected to MySQL server
140404 22:32:23 innobackupex: Executing a version check against the server...
140404 22:32:23 innobackupex: Done.
IMPORTANT: Please check that the backup run completes successfully.
At the end of a successful backup run innobackupex
prints "completed OK!".
innobackupex: Using mysql server version 5.6.16-
innobackupex: Created backup directory /root/backup/
140404 22:32:23 innobackupex: Starting ibbackup with command: xtrabackup_56 --defaults-
innobackupex: Waiting for ibbackup (pid=3084) to suspend
innobackupex: Suspend file '/root/
xtrabackup_56 version 2.1.8 for MySQL server 5.6.15 Linux (x86_64) (revision id: undefined)
xtrabackup: uses posix_fadvise().
xtrabackup: cd to /var/lib/mysql
xtrabackup: using the following InnoDB configuration:
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
>> log scanned up to (1626007)
[01] Copying ./ibdata1 to /root/backup/
[01] ...done
[01] Copying ./mysql/
[01] ...done
[01] Copying ./mysql/
[01] ...done
[01] Copying ./mysql/
[01] ...done
>> log scanned up to (1626007)
[01] Copying ./mysql/
[01] ...done
[01] Copying ./mysql/
[01] ...done
xtrabackup: Creating suspend file '/root/
140404 22:32:25 innobackupex: Continuing after ibbackup has suspended
140404 22:32:25 innobackupex: Starting to lock all tables...
>> log scanned up to (1626007)
140404 22:32:25 innobackupex: All tables locked and flushed to disk
140404 22:32:25 innobackupex: Starting to backup non-InnoDB tables and files
innobackupex: in subdirectories of '/var/lib/mysql'
innobackupex: Backing up files '/var/lib/
>> log scanned up to (1626007)
innobackupex: Backing up files '/var/lib/
>> log scanned up to (1626007)
140404 22:32:27 innobackupex: Finished backing up non-InnoDB tables and files
140404 22:32:27 innobackupex: Waiting for log copying to finish
xtrabackup: The latest check point (for incremental): '1626007'
xtrabackup: Stopping log copying thread.
.>> log scanned up to (1626007)
xtrabackup: Creating suspend file '/root/
xtrabackup: Transaction log of lsn (1626007) to (1626007) was copied.
140404 22:32:28 innobackupex: All tables unlocked
innobackupex: Backup created in directory '/root/
140404 22:32:28 innobackupex: Connection to database server closed
140404 22:32:28 innobackupex: completed OK!
root@ip-
InnoDB Backup Utility v1.5.1-xtrabackup; Copyright 2003, 2009 Innobase Oy
and Percona LLC and/or its affiliates 2009-2013. All Rights Reserved.
This software is published under
the GNU GENERAL PUBLIC LICENSE Version 2, June 1991.
Get the latest version of Percona XtraBackup, documentation, and help resources:
http://
IMPORTANT: Please check that the apply-log run completes successfully.
At the end of a successful apply-log run innobackupex
prints "completed OK!".
140404 22:32:58 innobackupex: Starting ibbackup with command: xtrabackup_56 --defaults-
xtrabackup_56 version 2.1.8 for MySQL server 5.6.15 Linux (x86_64) (revision id: undefined)
xtrabackup: cd to /root/backup/
xtrabackup: This target seems to be not prepared yet.
xtrabackup: xtrabackup_logfile detected: size=2097152, start_lsn=(1626007)
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
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: Using CPU crc32 instructions
InnoDB: Initializing buffer pool, size = 100.0M
InnoDB: Completed initialization of buffer pool
InnoDB: Highest supported file format is Barracuda.
InnoDB: The log sequence numbers 1625997 and 1625997 in ibdata files do not match the log sequence number 1626007 in the ib_logfiles!
InnoDB: Database was not shutdown normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages
InnoDB: from the doublewrite buffer...
InnoDB: 128 rollback segment(s) are active.
InnoDB: Waiting for purge to start
InnoDB: 5.6.15 started; log sequence number 1626007
[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_
InnoDB: FTS optimize thread exiting.
InnoDB: Starting shutdown...
InnoDB: Shutdown completed; log sequence number 1626017
140404 22:33:00 innobackupex: Restarting xtrabackup with command: xtrabackup_56 --defaults-
for creating ib_logfile*
xtrabackup_56 version 2.1.8 for MySQL server 5.6.15 Linux (x86_64) (revision id: undefined)
xtrabackup: cd to /root/backup/
xtrabackup: This target seems to be already prepared.
xtrabackup: notice: xtrabackup_logfile was already used to '--prepare'.
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
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: Using CPU crc32 instructions
InnoDB: Initializing buffer pool, size = 100.0M
InnoDB: Completed initialization of buffer pool
InnoDB: Setting log file ./ib_logfile101 size to 48 MB
InnoDB: Setting log file ./ib_logfile1 size to 48 MB
InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
InnoDB: New log files created, LSN=1626017
InnoDB: Highest supported file format is Barracuda.
InnoDB: 128 rollback segment(s) are active.
InnoDB: Waiting for purge to start
InnoDB: 5.6.15 started; log sequence number 1626124
[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_
InnoDB: FTS optimize thread exiting.
InnoDB: Starting shutdown...
InnoDB: Shutdown completed; log sequence number 1626134
140404 22:33:08 innobackupex: completed OK!
[[ no issue so far ]]
root@ip-
root@ip-
root@ip-
root@ip-
root@ip-
InnoDB Backup Utility v1.5.1-xtrabackup; Copyright 2003, 2009 Innobase Oy
and Percona LLC and/or its affiliates 2009-2013. All Rights Reserved.
This software is published under
the GNU GENERAL PUBLIC LICENSE Version 2, June 1991.
Get the latest version of Percona XtraBackup, documentation, and help resources:
http://
140404 22:40:13 innobackupex: Connecting to MySQL server with DSN 'dbi:mysql:
140404 22:40:13 innobackupex: Connected to MySQL server
140404 22:40:13 innobackupex: Executing a version check against the server...
140404 22:40:13 innobackupex: Done.
IMPORTANT: Please check that the backup run completes successfully.
At the end of a successful backup run innobackupex
prints "completed OK!".
innobackupex: Using mysql server version 5.6.16-
innobackupex: Created backup directory /root/backup/
140404 22:40:13 innobackupex: Starting ibbackup with command: xtrabackup_56 --defaults-
innobackupex: Waiting for ibbackup (pid=3418) to suspend
innobackupex: Suspend file '/root/
xtrabackup_56 version 2.1.8 for MySQL server 5.6.15 Linux (x86_64) (revision id: undefined)
xtrabackup: uses posix_fadvise().
xtrabackup: cd to /var/lib/mysql
xtrabackup: using the following InnoDB configuration:
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
>> log scanned up to (1634528)
[01] Copying ./ibdata1 to /root/backup/
>> log scanned up to (1634528)
>> log scanned up to (1634528)
[01] ...done
[01] Copying ./mysql/
[01] ...done
[01] Copying ./mysql/
[01] ...done
[01] Copying ./mysql/
[01] ...done
[01] Copying ./mysql/
[01] ...done
[01] Copying ./mysql/
[01] ...done
[01] Copying ./foo/bar.ibd to /root/backup/
[01] ...done
>> log scanned up to (1634528)
xtrabackup: Creating suspend file '/root/
140404 22:40:17 innobackupex: Continuing after ibbackup has suspended
140404 22:40:17 innobackupex: Starting to lock all tables...
140404 22:40:17 innobackupex: All tables locked and flushed to disk
140404 22:40:17 innobackupex: Starting to backup non-InnoDB tables and files
innobackupex: in subdirectories of '/var/lib/mysql'
innobackupex: Backing up files '/var/lib/
>> log scanned up to (1634528)
>> log scanned up to (1634528)
innobackupex: Backing up files '/var/lib/
>> log scanned up to (1634528)
innobackupex: Backing up file '/var/lib/
innobackupex: Backing up file '/var/lib/
140404 22:40:20 innobackupex: Finished backing up non-InnoDB tables and files
140404 22:40:20 innobackupex: Waiting for log copying to finish
xtrabackup: The latest check point (for incremental): '1634528'
xtrabackup: Stopping log copying thread.
.>> log scanned up to (1634528)
xtrabackup: Creating suspend file '/root/
xtrabackup: Transaction log of lsn (1634528) to (1634528) was copied.
140404 22:40:21 innobackupex: All tables unlocked
innobackupex: Backup created in directory '/root/
140404 22:40:21 innobackupex: Connection to database server closed
140404 22:40:21 innobackupex: completed OK!
root@ip-
InnoDB Backup Utility v1.5.1-xtrabackup; Copyright 2003, 2009 Innobase Oy
and Percona LLC and/or its affiliates 2009-2013. All Rights Reserved.
This software is published under
the GNU GENERAL PUBLIC LICENSE Version 2, June 1991.
Get the latest version of Percona XtraBackup, documentation, and help resources:
http://
IMPORTANT: Please check that the apply-log run completes successfully.
At the end of a successful apply-log run innobackupex
prints "completed OK!".
140404 22:40:51 innobackupex: Starting ibbackup with command: xtrabackup_56 --defaults-
xtrabackup_56 version 2.1.8 for MySQL server 5.6.15 Linux (x86_64) (revision id: undefined)
xtrabackup: cd to /root/backup/
xtrabackup: This target seems to be not prepared yet.
xtrabackup: xtrabackup_logfile detected: size=2097152, start_lsn=(1634528)
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
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: Using CPU crc32 instructions
InnoDB: Initializing buffer pool, size = 100.0M
InnoDB: Completed initialization of buffer pool
InnoDB: Highest supported file format is Barracuda.
InnoDB: The log sequence numbers 1625997 and 1625997 in ibdata files do not match the log sequence number 1634528 in the ib_logfiles!
InnoDB: Database was not shutdown normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages
InnoDB: from the doublewrite buffer...
InnoDB: 128 rollback segment(s) are active.
InnoDB: Waiting for purge to start
InnoDB: 5.6.15 started; log sequence number 1634528
[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_
InnoDB: FTS optimize thread exiting.
InnoDB: Starting shutdown...
InnoDB: Shutdown completed; log sequence number 1634538
140404 22:40:53 innobackupex: Restarting xtrabackup with command: xtrabackup_56 --defaults-
for creating ib_logfile*
xtrabackup_56 version 2.1.8 for MySQL server 5.6.15 Linux (x86_64) (revision id: undefined)
xtrabackup: cd to /root/backup/
xtrabackup: This target seems to be already prepared.
xtrabackup: notice: xtrabackup_logfile was already used to '--prepare'.
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
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: Using CPU crc32 instructions
InnoDB: Initializing buffer pool, size = 100.0M
InnoDB: Completed initialization of buffer pool
InnoDB: Setting log file ./ib_logfile101 size to 48 MB
InnoDB: Setting log file ./ib_logfile1 size to 48 MB
InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
InnoDB: New log files created, LSN=1634538
InnoDB: Highest supported file format is Barracuda.
InnoDB: 128 rollback segment(s) are active.
InnoDB: Waiting for purge to start
InnoDB: 5.6.15 started; log sequence number 1634828
[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_
InnoDB: FTS optimize thread exiting.
InnoDB: Starting shutdown...
InnoDB: Shutdown completed; log sequence number 1634838
140404 22:41:07 innobackupex: completed OK!
root@ip-
root@ip-
root@ip-
root@ip-
* Stopping MySQL (Percona Server) mysqld [ OK ]
* Starting MySQL (Percona Server) database server mysqld [ OK ]
* Checking for corrupt, not cleanly closed and upgrade needing tables.
root@ip-
root@ip-
root@ip-
InnoDB Backup Utility v1.5.1-xtrabackup; Copyright 2003, 2009 Innobase Oy
and Percona LLC and/or its affiliates 2009-2013. All Rights Reserved.
This software is published under
the GNU GENERAL PUBLIC LICENSE Version 2, June 1991.
Get the latest version of Percona XtraBackup, documentation, and help resources:
http://
140404 22:47:14 innobackupex: Connecting to MySQL server with DSN 'dbi:mysql:
140404 22:47:14 innobackupex: Connected to MySQL server
140404 22:47:14 innobackupex: Executing a version check against the server...
140404 22:47:14 innobackupex: Done.
IMPORTANT: Please check that the backup run completes successfully.
At the end of a successful backup run innobackupex
prints "completed OK!".
innobackupex: Using mysql server version 5.6.16-
innobackupex: Created backup directory /root/backup/
140404 22:47:14 innobackupex: Starting ibbackup with command: xtrabackup_56 --defaults-
innobackupex: Waiting for ibbackup (pid=4091) to suspend
innobackupex: Suspend file '/root/
xtrabackup_56 version 2.1.8 for MySQL server 5.6.15 Linux (x86_64) (revision id: undefined)
xtrabackup: uses posix_fadvise().
xtrabackup: cd to /var/lib/mysql
xtrabackup: using the following InnoDB configuration:
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
>> log scanned up to (1650076)
[01] Copying ./ibdata1 to /root/backup/
>> log scanned up to (1650076)
[01] ...done
[01] Copying ./mysql/
[01] ...done
[01] Copying ./mysql/
[01] ...done
[01] Copying ./mysql/
[01] ...done
[01] Copying ./mysql/
[01] ...done
[01] Copying ./mysql/
[01] ...done
[01] Copying ./foo/baz.ibd to /root/backup/
[01] ...done
[01] Copying ./foo/bar.ibd to /root/backup/
[01] ...done
>> log scanned up to (1650076)
xtrabackup: Creating suspend file '/root/
140404 22:47:17 innobackupex: Continuing after ibbackup has suspended
140404 22:47:17 innobackupex: Starting to lock all tables...
140404 22:47:17 innobackupex: All tables locked and flushed to disk
140404 22:47:17 innobackupex: Starting to backup non-InnoDB tables and files
innobackupex: in subdirectories of '/var/lib/mysql'
innobackupex: Backing up files '/var/lib/
>> log scanned up to (1650076)
>> log scanned up to (1650076)
innobackupex: Backing up files '/var/lib/
>> log scanned up to (1650076)
innobackupex: Backing up file '/var/lib/
innobackupex: Backing up file '/var/lib/
innobackupex: Backing up file '/var/lib/
140404 22:47:20 innobackupex: Finished backing up non-InnoDB tables and files
140404 22:47:20 innobackupex: Waiting for log copying to finish
xtrabackup: The latest check point (for incremental): '1650076'
xtrabackup: Stopping log copying thread.
.>> log scanned up to (1650076)
xtrabackup: Creating suspend file '/root/
xtrabackup: Transaction log of lsn (1650076) to (1650076) was copied.
140404 22:47:21 innobackupex: All tables unlocked
innobackupex: Backup created in directory '/root/
140404 22:47:21 innobackupex: Connection to database server closed
140404 22:47:21 innobackupex: completed OK!
root@ip-
InnoDB Backup Utility v1.5.1-xtrabackup; Copyright 2003, 2009 Innobase Oy
and Percona LLC and/or its affiliates 2009-2013. All Rights Reserved.
This software is published under
the GNU GENERAL PUBLIC LICENSE Version 2, June 1991.
Get the latest version of Percona XtraBackup, documentation, and help resources:
http://
IMPORTANT: Please check that the apply-log run completes successfully.
At the end of a successful apply-log run innobackupex
prints "completed OK!".
140404 22:47:47 innobackupex: Starting ibbackup with command: xtrabackup_56 --defaults-
xtrabackup_56 version 2.1.8 for MySQL server 5.6.15 Linux (x86_64) (revision id: undefined)
xtrabackup: cd to /root/backup/
xtrabackup: This target seems to be not prepared yet.
xtrabackup: xtrabackup_logfile detected: size=2097152, start_lsn=(1650076)
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
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: Using CPU crc32 instructions
InnoDB: Initializing buffer pool, size = 100.0M
InnoDB: Completed initialization of buffer pool
InnoDB: Highest supported file format is Barracuda.
InnoDB: The log sequence numbers 1650066 and 1650066 in ibdata files do not match the log sequence number 1650076 in the ib_logfiles!
InnoDB: Database was not shutdown normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages
InnoDB: from the doublewrite buffer...
InnoDB: 128 rollback segment(s) are active.
InnoDB: Waiting for purge to start
2014-04-04 22:47:48 7f9731df5700 InnoDB: Warning: table 'mysql/
InnoDB: in InnoDB data dictionary has unknown flags 50.
2014-04-04 22:47:48 7f9731df5700 InnoDB: Warning: table 'mysql/
InnoDB: in InnoDB data dictionary has unknown flags 50.
InnoDB: 5.6.15 started; log sequence number 1650076
[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_
InnoDB: FTS optimize thread exiting.
InnoDB: Starting shutdown...
InnoDB: Shutdown completed; log sequence number 1650086
140404 22:47:49 innobackupex: Restarting xtrabackup with command: xtrabackup_56 --defaults-
for creating ib_logfile*
xtrabackup_56 version 2.1.8 for MySQL server 5.6.15 Linux (x86_64) (revision id: undefined)
xtrabackup: cd to /root/backup/
xtrabackup: This target seems to be already prepared.
xtrabackup: notice: xtrabackup_logfile was already used to '--prepare'.
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
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: Using CPU crc32 instructions
InnoDB: Initializing buffer pool, size = 100.0M
InnoDB: Completed initialization of buffer pool
InnoDB: Setting log file ./ib_logfile101 size to 48 MB
InnoDB: Setting log file ./ib_logfile1 size to 48 MB
InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
InnoDB: New log files created, LSN=1650086
InnoDB: Highest supported file format is Barracuda.
InnoDB: 128 rollback segment(s) are active.
InnoDB: Waiting for purge to start
2014-04-04 22:47:56 7f5e32d84700 InnoDB: Warning: table 'mysql/
InnoDB: in InnoDB data dictionary has unknown flags 50.
2014-04-04 22:47:56 7f5e32d84700 InnoDB: Warning: table 'mysql/
InnoDB: in InnoDB data dictionary has unknown flags 50.
InnoDB: 5.6.15 started; log sequence number 1650188
[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_
InnoDB: FTS optimize thread exiting.
InnoDB: Starting shutdown...
InnoDB: Shutdown completed; log sequence number 1650198
140404 22:47:57 innobackupex: completed OK!
Related branches
- Sergei Glushchenko (community): Approve (g2)
-
Diff: 1167 lines (+193/-129)3 files modifiedMakefile (+1/-1)
patches/innodb56.patch (+190/-126)
utils/build.sh (+2/-2)
tags: | added: i41366 |
Oh, for what it's worth, the issue gets worse with time...:
InnoDB: Reading tablespace information from the .ibd files... innodb_ index_stats' innodb_ table_stats' EmployeeLogin' GeneralLedger' PaymentDetail' CashDrawer' Category' ItemInstance' InventoryLog' CompanyConfigur ation' CompanyFeature' CompanyHours' Company_ Tr' Customer' CustomerLogin' CustomerText_ Tr' Transaction'
InnoDB: Restoring possible half-written data pages
InnoDB: from the doublewrite buffer...
InnoDB: Last MySQL binlog file position 0 22051, file name mysql-bin.000008
InnoDB: 128 rollback segment(s) are active.
InnoDB: Waiting for purge to start
2014-04-04 23:04:51 7f5ded3f3700 InnoDB: Warning: table 'mysql/
InnoDB: in InnoDB data dictionary has unknown flags 50.
2014-04-04 23:04:51 7f5ded3f3700 InnoDB: Warning: table 'mysql/
InnoDB: in InnoDB data dictionary has unknown flags 50.
2014-04-04 23:04:51 7f5ded3f3700 InnoDB: Warning: table 'prod00009/
InnoDB: in InnoDB data dictionary has unknown flags 50.
2014-04-04 23:04:51 7f5ded3f3700 InnoDB: Warning: table 'prod00009/Company'
InnoDB: in InnoDB data dictionary has unknown flags 50.
2014-04-04 23:04:51 7f5ded3f3700 InnoDB: Warning: table 'prod00009/Account'
InnoDB: in InnoDB data dictionary has unknown flags 50.
2014-04-04 23:04:51 7f5ded3f3700 InnoDB: Warning: table 'prod00009/
InnoDB: in InnoDB data dictionary has unknown flags 50.
2014-04-04 23:04:51 7f5ded3f3700 InnoDB: Warning: table 'prod00009/Payment'
InnoDB: in InnoDB data dictionary has unknown flags 50.
2014-04-04 23:04:51 7f5ded3f3700 InnoDB: Warning: table 'prod00009/
InnoDB: in InnoDB data dictionary has unknown flags 50.
2014-04-04 23:04:51 7f5ded3f3700 InnoDB: Warning: table 'prod00009/
InnoDB: in InnoDB data dictionary has unknown flags 50.
2014-04-04 23:04:51 7f5ded3f3700 InnoDB: Warning: table 'prod00009/
InnoDB: in InnoDB data dictionary has unknown flags 50.
2014-04-04 23:04:51 7f5ded3f3700 InnoDB: Warning: table 'prod00009/Item'
InnoDB: in InnoDB data dictionary has unknown flags 50.
2014-04-04 23:04:51 7f5ded3f3700 InnoDB: Warning: table 'prod00009/
InnoDB: in InnoDB data dictionary has unknown flags 50.
2014-04-04 23:04:51 7f5ded3f3700 InnoDB: Warning: table 'prod00009/
InnoDB: in InnoDB data dictionary has unknown flags 50.
2014-04-04 23:04:51 7f5ded3f3700 InnoDB: Warning: table 'prod00009/
InnoDB: in InnoDB data dictionary has unknown flags 50.
2014-04-04 23:04:51 7f5ded3f3700 InnoDB: Warning: table 'prod00009/
InnoDB: in InnoDB data dictionary has unknown flags 50.
2014-04-04 23:04:51 7f5ded3f3700 InnoDB: Warning: table 'prod00009/
InnoDB: in InnoDB data dictionary has unknown flags 50.
2014-04-04 23:04:51 7f5ded3f3700 InnoDB: Warning: table 'prod00009/
InnoDB: in InnoDB data dictionary has unknown flags 50.
2014-04-04 23:04:51 7f5ded3f3700 InnoDB: Warning: table 'prod00009/
InnoDB: in InnoDB data dictionary has unknown flags 50.
2014-04-04 23:04:51 7f5ded3f3700 InnoDB: Warning: table 'prod00009/
InnoDB: in InnoDB data dictionary has unknown flags 50.
2014-04-04 23:04:51 7f5ded3f3700 InnoDB: Warning: table 'prod00009/
InnoDB: in InnoDB data dictionary has unknown flags 50.
2014-04-04 23:04:51 7f5ded3f3700 InnoDB: Warning: table 'prod00009/
InnoD...