Description:
Assertion failure in file /export/home/pb2/build/sb_0-18784902-1462436607.89/mysqlcom-pro-5.6.29/storage/innobase/page/page0zip.cc line 4236
###############################################################################
...
171206 11:09:00 mysqlbackup_64bit_312: INFO: Compressed files removed successfully
171206 11:09:00 mysqlbackup_64bit_312: INFO: Uncompress operation completed successfully.
mysqlbackup_64bit_312: INFO: Creating 12 buffers each of size 65678.
171206 11:09:00 mysqlbackup_64bit_312: INFO: Apply-log operation starts with following threads
1 read-threads 1 process-threads
mysqlbackup_64bit_312: INFO: Using up to 300 MB of memory.
171206 11:09:00 mysqlbackup_64bit_312: INFO: ibbackup_logfile's creation parameters:
start lsn 14246244000256, end lsn 14250261334763,
start checkpoint 14246244000697.
InnoDB: Doing recovery: scanned up to log sequence number 14246249243136
InnoDB: Doing recovery: scanned up to log sequence number 14246254486016
InnoDB: Doing recovery: scanned up to log sequence number 14246259728896
InnoDB: Doing recovery: scanned up to log sequence number 14246264971776
InnoDB: Doing recovery: scanned up to log sequence number 14246270214656
InnoDB: Doing recovery: scanned up to log sequence number 14246275457536
InnoDB: Doing recovery: scanned up to log sequence number 14246280700416
InnoDB: Doing recovery: scanned up to log sequence number 14246285943296
InnoDB: Doing recovery: scanned up to log sequence number 14246291186176
InnoDB: Doing recovery: scanned up to log sequence number 14246296429056
InnoDB: Doing recovery: scanned up to log sequence number 14246301671936
InnoDB: Doing recovery: scanned up to log sequence number 14246306914816
InnoDB: Doing recovery: scanned up to log sequence number 14246312157696
InnoDB: Doing recovery: scanned up to log sequence number 14246317400576
InnoDB: Doing recovery: scanned up to log sequence number 14246322643456
InnoDB: Doing recovery: scanned up to log sequence number 14246327886336
InnoDB: Doing recovery: scanned up to log sequence number 14246333129216
InnoDB: Doing recovery: scanned up to log sequence number 14246338372096
mysqlbackup_64bit_312: INFO: InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 0 1 2 3 4 5 6 7 8 9 10 2017-12-06 11:09:05 7fc25bfff700 InnoDB: Assertion failure in file /export/home/pb2/build/sb_0-18784902-1462436607.89/mysqlcom-pro-5.6.29/storage/innobase/page/page0zip.cc line 4236
InnoDB: Failing assertion: slot
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.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
How to repeat:
After copying the backup file and uncompressing, a message confirms that the operation is successful, but errors occur.
Description: Assertion failure in file /export/home/pb2/build/sb_0-18784902-1462436607.89/mysqlcom-pro-5.6.29/storage/innobase/page/page0zip.cc line 4236 ############################################################################### ... 171206 11:09:00 mysqlbackup_64bit_312: INFO: Compressed files removed successfully 171206 11:09:00 mysqlbackup_64bit_312: INFO: Uncompress operation completed successfully. mysqlbackup_64bit_312: INFO: Creating 12 buffers each of size 65678. 171206 11:09:00 mysqlbackup_64bit_312: INFO: Apply-log operation starts with following threads 1 read-threads 1 process-threads mysqlbackup_64bit_312: INFO: Using up to 300 MB of memory. 171206 11:09:00 mysqlbackup_64bit_312: INFO: ibbackup_logfile's creation parameters: start lsn 14246244000256, end lsn 14250261334763, start checkpoint 14246244000697. InnoDB: Doing recovery: scanned up to log sequence number 14246249243136 InnoDB: Doing recovery: scanned up to log sequence number 14246254486016 InnoDB: Doing recovery: scanned up to log sequence number 14246259728896 InnoDB: Doing recovery: scanned up to log sequence number 14246264971776 InnoDB: Doing recovery: scanned up to log sequence number 14246270214656 InnoDB: Doing recovery: scanned up to log sequence number 14246275457536 InnoDB: Doing recovery: scanned up to log sequence number 14246280700416 InnoDB: Doing recovery: scanned up to log sequence number 14246285943296 InnoDB: Doing recovery: scanned up to log sequence number 14246291186176 InnoDB: Doing recovery: scanned up to log sequence number 14246296429056 InnoDB: Doing recovery: scanned up to log sequence number 14246301671936 InnoDB: Doing recovery: scanned up to log sequence number 14246306914816 InnoDB: Doing recovery: scanned up to log sequence number 14246312157696 InnoDB: Doing recovery: scanned up to log sequence number 14246317400576 InnoDB: Doing recovery: scanned up to log sequence number 14246322643456 InnoDB: Doing recovery: scanned up to log sequence number 14246327886336 InnoDB: Doing recovery: scanned up to log sequence number 14246333129216 InnoDB: Doing recovery: scanned up to log sequence number 14246338372096 mysqlbackup_64bit_312: INFO: InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percent: 0 1 2 3 4 5 6 7 8 9 10 2017-12-06 11:09:05 7fc25bfff700 InnoDB: Assertion failure in file /export/home/pb2/build/sb_0-18784902-1462436607.89/mysqlcom-pro-5.6.29/storage/innobase/page/page0zip.cc line 4236 InnoDB: Failing assertion: slot 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.6/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. How to repeat: After copying the backup file and uncompressing, a message confirms that the operation is successful, but errors occur.