Sometimes the following phenomena occur.
When applies the log at new page, the page seems to be not exist yet.
> ./xtrabackup --prepare
./xtrabackup Ver alpha-0.3 for 5.0.75 unknown-linux-gnu (x86_64)
xtrabackup_logfile detected: size=4603904, start_lsn=(0 1597327805)
InnoDB: Log scan progressed past the checkpoint lsn 0 1597327805
090324 20:21:40 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 0 1601920875
090324 20:21:40 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 11 12 InnoDB: Error: trying to access page number 0 in space 68,
InnoDB: space name ./tpcc/new_orders.ibd,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 16384, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
090324 20:21:41InnoDB: Assertion failure in thread 47082044570368 in file fil0fil.c line 3959
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: about forcing recovery.
The fix has been pushed.
http://
added patches to InnoDB