| Bug #68222 | InnoDB: Assertion Failure in file | ||
|---|---|---|---|
| Submitted: | 30 Jan 2013 8:20 | Modified: | 5 Feb 2013 15:05 |
| Reporter: | Wooyong Shin | Email Updates: | |
| Status: | Duplicate | Impact on me: | |
| Category: | MySQL Enterprise Backup | Severity: | S3 (Non-critical) |
| Version: | 5.5.27 | OS: | Linux |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | Enterprise Backup, Failing assertion ;!*data, innodb | ||
[30 Jan 2013 16:46]
Sveta Smirnova
Thank you for the report. Which exact version of MEB do you use? Please also send full log of command you use to call mysqlbackup.
[31 Jan 2013 1:35]
Wooyong Shin
MySQL Enterprise Backup version 3.7.1 [2012/03/20]
Copyright (c) 2003, 2012, Oracle and/or its affiliates. All Rights Reserved.
INFO: Starting with following command line ...
/home01/sys/meb/mysqlbackup --defaults-file=/etc/my.cnf -uroot -pxxxxxxx
--backup-dir=/cms/mdb/backup/201301310001/bkpimage backup-and-apply-log
[1 Feb 2013 2:25]
Wooyong Shin
Another Server's error message. Same MySQL,MEB version and same MEB Command.
Error message is different. but occurred when "apply batch of log records to the database....." same as above.
I have't backed up nowadays. It could be a tragedy.
Do I have to register new bug ?
----------------------------------------------------------------
......
mysqlbackup: INFO: A copied database page was modified at 4498148300361.
(This is the highest lsn found on page)
Scanned log up to lsn 4498148789576.
Was able to parse the log up to lsn 4498148789576.
Maximum page number for a log record 2293632
130201 00:30:16 mysqlbackup: INFO: All tables unlocked
mysqlbackup: INFO: All MySQL tables were locked for 2.000 seconds
130201 0:30:16 mysqlbackup: INFO: Full backup completed!
mysqlbackup: INFO: MySQL binlog position: filename mysql-bin.001426, position 791873274
mysqlbackup: INFO: Backup created in directory '/cms/mdb/backup/201302010001/bkpimage'
130201 0:30:16 mysqlbackup: INFO: ibbackup_logfile's creation parameters:
start lsn 4497856579072, end lsn 4498148789576,
start checkpoint 4497856579346.
InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 130201 0:35:58 InnoDB: Assertion failure in file /pb2/build_bi/sb_7-5288320-1332255884.52/src/innodb/rem/rem0rec.c line 561
[1 Feb 2013 8:32]
MySQL Verification Team
Isn't it: Bug 14704347 - APPLY-LOG FAILING WITH ERROR - FAILING ASSERTION: !*DATA
[5 Feb 2013 15:05]
MySQL Verification Team
Please try MySQL Enterprise Backup 3.8.1 has been released which contains a fix for this.
Description: I get error often when I execute backup using Enterprise Backup Tool. Error message is below. .... 130129 0:37:58 mysqlbackup: INFO: Copying /cms/mdb/dbdf/astore/tacm_appl_itm_fake_ord.ibd (Barracuda file format). 130129 0:37:58 mysqlbackup: INFO: Copying /cms/mdb/dbdf/sbtest/sbtest.ibd (Antelope file format). mysqlbackup: INFO: Preparing to lock tables: Connected to mysqld server. 130129 00:37:59 mysqlbackup: INFO: Starting to lock all the tables.... 130129 00:37:59 mysqlbackup: INFO: All tables are locked and flushed to disk mysqlbackup: INFO: Opening backup source directory '/cms/mdb/dbdf/' 130129 00:37:59 mysqlbackup: INFO: Starting to backup all files in subdirectories of '/cms/mdb/dbdf/' mysqlbackup: INFO: Backing up the database directory 'astore' mysqlbackup: INFO: Backing up the database directory 'mysql' mysqlbackup: INFO: Backing up the database directory 'performance_schema' mysqlbackup: INFO: Backing up the database directory 'sbtest' mysqlbackup: INFO: Backing up the database directory 'test' mysqlbackup: INFO: Copying innodb data and logs during final stage ... mysqlbackup: INFO: A copied database page was modified at 4561287417389. (This is the highest lsn found on page) Scanned log up to lsn 4561287904346. Was able to parse the log up to lsn 4561287904346. Maximum page number for a log record 3565743 130129 00:38:01 mysqlbackup: INFO: All tables unlocked mysqlbackup: INFO: All MySQL tables were locked for 2.000 seconds 130129 0:38:01 mysqlbackup: INFO: Full backup completed! mysqlbackup: INFO: MySQL binlog position: filename mysql-bin.001373, position 666057883 mysqlbackup: INFO: Backup created in directory '/cms/mdb/backup/201301290001/bkpimage' 130129 0:38:01 mysqlbackup: INFO: ibbackup_logfile's creation parameters: start lsn 4560977596416, end lsn 4561287904346, start checkpoint 4560977596494. InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 130129 0:44:52 InnoDB: Assertion failure in file /pb2/build_bi/sb_7-5288320-1332255884.52/src/innodb/page/page0zip.c line 3552 InnoDB: Failing assertion: !*data 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. How to repeat: 2 or 3 time a week.