[root@murr tmp]# cat xtrabackup_backupfiles/backup-my.cnf
# This MySQL options file was generated by innobackup.
# The MySQL server
[mysqld]
datadir=/tmp
innodb_data_home_dir=/tmp
innodb_data_file_path=ibdata1:10M:autoextend
innodb_log_group_home_dir=/tmp
innodb_log_files_in_group=2
innodb_log_file_size=67108864
xtrabackup --prepare
xtrabackup Ver 0.9 Rev 83 for 5.0.84 unknown-linux-gnu (x86_64)
xtrabackup: cd to ./xtrabackup_backupfiles/
xtrabackup: This target seems to be not prepared yet.
090923 21:58:21 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
xtrabackup: Warning: cannot open ./xtrabackup_logfile. will try to find.
xtrabackup: 'ib_logfile0' seems to be 'xtrabackup_logfile'. will retry.
xtrabackup: xtrabackup_logfile detected: size=10682368, start_lsn=(145 3582940994)
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 = 10682368
xtrabackup: Starting InnoDB instance for recovery.
xtrabackup: Using 104857600 bytes for buffer pool (set by --use-memory parameter)
InnoDB: Log scan progressed past the checkpoint lsn 145 3582940994
090923 21:58:21 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: ############### CORRUPT LOG RECORD FOUND
InnoDB: Log record type 50, space id 509, page number 928702
InnoDB: Log parsing proceeded successfully up to 145 3582942359
InnoDB: Previous log record type 14, is multi 1
InnoDB: Recv offset 1368, prev 1362
InnoDB: Hex dump of corrupt log starting 100 bytes before the start
InnoDB: of the previous log rec,
InnoDB: and ending 100 bytes after the start of the corrupt rec:
len 206; hex 0465eda681cece8e6f00020002000080081dd20465ed02002d0038020400053c46c0b5120400053a52e5e17f11040005385ee5e17e801f2681fdce2bbe0002000200048008235e0861159d470e00b0fd0fc92681fdce2bbe0002000200048008234c02510e00b0fd0ff73281fdce2bbe300200000181fdce2001063d321f2681cec3191600020002000080083183064ee0590e00a5170ebd0281cec319160030000181cec300010ce9031fa681fdce5c390002000200008008113f06ea8c3d8e00a9f40d6fa681fdce5c39000200; asc e o e - 8 <F :R 8^ ~ & + #^ a G & + #L Q 2 + 0 =2 & 1 N Y 0 \9 ? = o \9 ;
InnoDB: WARNING: the log file may have been corrupt and it
InnoDB: is possible that the log scan did not proceed
InnoDB: far enough in recovery! Please run CHECK TABLE
InnoDB: on your InnoDB tables to check that they are ok!
InnoDB: If mysqld crashes after this recovery, look at
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: about forcing recovery.
InnoDB: Doing recovery: scanned up to log sequence number 145 3588183552 (55 %)
InnoDB: Doing recovery: scanned up to log sequence number 145 3591384476 (88 %)
090923 21:58:21 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 1 2 3 090923 21:58:21InnoDB: Assertion failure in thread 1142401344 in file log0recv.c line 886
InnoDB: Failing assertion: !page || (ibool)!!page_is_comp(page)==index->table->comp
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 problem should be fixed in 1.4