Bug #61926 InnoDB: Assertion failure in file .\innodb\fil\fil0fil.c line 664

• Submitted: 20 Jul 2011 11:23
• Modified: 6 Aug 2011 12:00
• Reporter: Chuks Aguocha
• Status: Not a Bug
• Category: MySQL Server: Backup
• Severity: S3 (Non-critical)
• Version: 5.1.57-community-log
• OS: Any
• CPU Architecture: Any

[20 Jul 2011 11:23] Chuks Aguocha

Description:

C:\Program Files\MySQL\MySQL Enterprise Backup 3.6\bin>innobackup --apply-log  /
backups/3308/2011-07-20_11-37-46/backup-my.cnf /backups/3308/2011-07-20_11-37
-46 >>NonIBBbackuplog3308.txt
ibbackup version 3.6.0 MySQL Enterprise Backup version 3.6.0 [01.07.2011 ]
Copyright (c) 2003, 2011, Oracle and/or its affiliates. All Rights Reserved.
Run 'ibbackup --help' for help and 'ibbackup --version' for version info.

Contents of \backups\3308\2011-07-20_11-37-46\backup-my.cnf:
innodb_data_home_dir got value \backups\3308\2011-07-20_11-37-46
innodb_data_file_path got value ibdata1:10M:autoextend
datadir got value \backups\3308\2011-07-20_11-37-46
innodb_log_group_home_dir got value \backups\3308\2011-07-20_11-37-46
innodb_log_files_in_group got value 2
innodb_log_file_size got value 46137344

110720 12:03:33110720 12:03:33  InnoDB: Operating system error number 2 in a fil
e operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/operating-system-error-codes.html

110720 12:03:33  InnoDB: Fatal error: cannot open \backups\3308\2011-07-20_11-37
-46\ibdata1
.InnoDB: Have you deleted .ibd files under a running mysqld server?
110720 12:03:33  InnoDB: Assertion failure in file .\innodb\fil\fil0fil.c line 6
64
InnoDB: Failing assertion: 0
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.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
 innobackup: ERROR: mysqlbackup "apply-log" failed

How to repeat:
MySQL Enterprise backup version 3.6

1. perform innobackup --user= --password= --compress myNonIBB3308.ini /backups/3308

completes successfully

2. perform innobackup --apply-log  /
backups/3308/2011-07-20_11-37-46/backup-my.cnf /backups/3308/2011-07-20_11-37
-46 >>NonIBBbackuplog3308.txt

[6 Aug 2011 12:00] Sveta Smirnova

Thank you for taking the time to write to us, but this is not a bug. Please double-check the documentation available at http://dev.mysql.com/doc/ and the instructions on
how to report a bug at http://bugs.mysql.com/how-to-report.php

You should specify --uncompress option