percona-discussion team mailing list archive

[Vadim Tkachenko <vadim@xxxxxxxxxxx>]

Public bug reported:

xtrabackup  Ver rc-0.7 for 5.0.77 unknown-linux-gnu (x86_64)
xtrabackup: cd to /wl/connect1_bck/2009-05-15_00-33-47/2009-05-24_00-30-02/
xtrabackup: This target seems to be not prepared yet.
xtrabackup: xtrabackup_logfile detected: size=1887535104, start_lsn=(856 1835663170)
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 = 1887535104
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 856 1835663170
090524 23:44:01  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Doing recovery: scanned up to log sequence number 856 1840905728 (0 %)
InnoDB: Doing recovery: scanned up to log sequence number 856 1846148608 (0 %)
InnoDB: Doing recovery: scanned up to log sequence number 856 1851391488 (0 %)
InnoDB: Doing recovery: scanned up to log sequence number 856 1856634368 (1 %)
InnoDB: Doing recovery: scanned up to log sequence number 856 1861877248 (1 %)
InnoDB: Doing recovery: scanned up to log sequence number 856 1867120128 (1 %)
090524 23:44:04  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 090525  0:00:41InnoDB: Assertion failure in thread 1115699552 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.
InnoDB: Thread 182894071520 stopped in file ./../include/sync0sync.ic line 111

** Affects: percona-xtrabackup
     Importance: Undecided
         Status: New

-- 
crash on  --prepare
https://bugs.launchpad.net/bugs/380431
You received this bug notification because you are a member of Percona
developers, which is the registrant for Percona-XtraBackup.

Status in Open source backup tool for InnoDB and XtraDB: New

Bug description:
xtrabackup  Ver rc-0.7 for 5.0.77 unknown-linux-gnu (x86_64)
xtrabackup: cd to /wl/connect1_bck/2009-05-15_00-33-47/2009-05-24_00-30-02/
xtrabackup: This target seems to be not prepared yet.
xtrabackup: xtrabackup_logfile detected: size=1887535104, start_lsn=(856 1835663170)
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 = 1887535104
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 856 1835663170
090524 23:44:01  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Doing recovery: scanned up to log sequence number 856 1840905728 (0 %)
InnoDB: Doing recovery: scanned up to log sequence number 856 1846148608 (0 %)
InnoDB: Doing recovery: scanned up to log sequence number 856 1851391488 (0 %)
InnoDB: Doing recovery: scanned up to log sequence number 856 1856634368 (1 %)
InnoDB: Doing recovery: scanned up to log sequence number 856 1861877248 (1 %)
InnoDB: Doing recovery: scanned up to log sequence number 856 1867120128 (1 %)
090524 23:44:04  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 090525  0:00:41InnoDB: Assertion failure in thread 1115699552 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.
InnoDB: Thread 182894071520 stopped in file ./../include/sync0sync.ic line 111