LP #1604299: InnoDB: Progress in percent: InnoDB: Trying to access page number 49664 in space 0, space name innodb_system, which is outside the tablespace bounds

**Reported in Launchpad by Shahriyar Rzayev last update 21-07-2016 12:15:35

Testing with MySQL 5.5.50 Master-Slave replication setup on master side.

Running sysbench:

sysbench --test=/usr/share/doc/sysbench/tests/db/insert.lua --oltp-test-mode=complex --num-threads=100 --mysql-db=dbtest --mysql-host=127.0.0.1 --mysql-user=root --mysql-password=msandbox --db-driver=mysql --max-requests=0 --mysql-socket=/tmp/mysql_sandbox26605.sock --mysql-port=26605 run

The result of prepare stage on incremental backup:

/usr/local/xtrabackup/bin/xtrabackup version 2.4.3 based on MySQL server 5.7.13 Linux (x86_64) (revision id: 2d5c4c0)
incremental backup from 1397056875 is enabled.
xtrabackup: cd to /home/backup_dir/full
xtrabackup: This target seems to be already prepared with --apply-log-only.
InnoDB: Number of pools: 1
xtrabackup: xtrabackup_logfile detected: size=9568256, start_lsn=(1451544875)
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup: innodb_data_home_dir = .
xtrabackup: innodb_data_file_path = ibdata1:10M:autoextend
xtrabackup: innodb_log_group_home_dir = /home/backup_dir/inc/inc3
xtrabackup: innodb_log_files_in_group = 1
xtrabackup: innodb_log_file_size = 9568256
xtrabackup: Generating a list of tablespaces
xtrabackup: page size for /home/backup_dir/inc/inc3/ibdata1.delta is 16384 bytes
Applying /home/backup_dir/inc/inc3/ibdata1.delta to ./ibdata1...
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup: innodb_data_home_dir = .
xtrabackup: innodb_data_file_path = ibdata1:10M:autoextend
xtrabackup: innodb_log_group_home_dir = /home/backup_dir/inc/inc3
xtrabackup: innodb_log_files_in_group = 1
xtrabackup: innodb_log_file_size = 9568256
xtrabackup: Starting InnoDB instance for recovery.
xtrabackup: Using 104857600 bytes for buffer pool (set by --use-memory parameter)
InnoDB: PUNCH HOLE support available
InnoDB: !!!!!!!! UNIV_DEBUG switched on !!!!!!!!!
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Uses event mutexes
InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
InnoDB: Compressed tables use zlib 1.2.7
InnoDB: Number of pools: 1
InnoDB: Using CPU crc32 instructions
InnoDB: Initializing buffer pool, total size = 100M, instances = 1, chunk size = 100M
InnoDB: Completed initialization of buffer pool
InnoDB: page_cleaner coordinator priority: -20
InnoDB: Highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 1451544875
InnoDB: Doing recovery: scanned up to log sequence number 1456787456 (61%)
InnoDB: Doing recovery: scanned up to log sequence number 1460011922 (99%)
InnoDB: Doing recovery: scanned up to log sequence number 1453510656 (23%)
InnoDB: Doing recovery: scanned up to log sequence number 1458753536 (84%)
InnoDB: Doing recovery: scanned up to log sequence number 1460011922 (99%)
InnoDB: Database was not shutdown normally!
InnoDB: Starting crash recovery.
InnoDB: Doing recovery: scanned up to log sequence number 1455476736 (46%)
InnoDB: Doing recovery: scanned up to log sequence number 1460011922 (99%)
InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: InnoDB: Trying to access page number 49664 in space 0, space name innodb_system, which is outside the tablespace bounds. Byte offset 0, len 16384, i/o type read. If you get this error at mysqld startup, please check that your my.cnf matches the ibdata files that you have in the MySQL server.
InnoDB: Server exits at /root/percona-xtrabackup/storage/innobase/fil/fil0fil.cc[5636].

Please see attachment for backup and prepare scripts.