Bug #58439 Attempt to apply incremental backup to 'unapplyied' full backup causes a crash
Submitted: 24 Nov 2010 2:28 Modified: 12 Oct 2011 18:37
Reporter: Alexey Stroganov Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Enterprise Backup Severity:S3 (Non-critical)
Version:3.5.2 OS:Any
Assigned to: CPU Architecture:Any
Triage: Triaged: D2 (Serious)

[24 Nov 2010 2:28] Alexey Stroganov
Description:
1) I've created full backup of DB (full_backup)
2) a bit later I've created incremental backup(inc_backup)
3) I've skipped execution of ibbackup --apply-log for full_backup 
4) I've run ibbackup --apply-log --incremental <full backup.cnf> <inc backup.cnf>
5) I got a crash (see below)
 
Please note that at 4) I've put config files in wrong order intentionally.

-------------------------------------------------------

ibbackup version 3.5.2 MySQL Enterprise Backup 3.5.2
Copyright (c) 2002, 2010, Oracle and/or its affiliates.
Run 'ibbackup --help' for help and 'ibbackup --version' for version info.

Note: Uses posix_fadvise() for performance optimization.

Contents of 2010-11-24_02-02-33/backup-my.cnf:
innodb_data_home_dir got value /data0/meb/2010-11-24_02-02-33
innodb_data_file_path got value ibdata1:100M:autoextend
datadir got value /data0/meb/2010-11-24_02-02-33
innodb_log_group_home_dir got value /data0/meb/2010-11-24_02-02-33
innodb_log_files_in_group got value 2
innodb_log_file_size got value 681574400

Contents of 2010-11-24_02-06-34/backup-my.cnf:
innodb_data_home_dir got value /data0/meb/2010-11-24_02-06-34
innodb_data_file_path got value ibdata1:100M:autoextend
datadir got value /data0/meb/2010-11-24_02-06-34
innodb_log_group_home_dir got value /data0/meb/2010-11-24_02-06-34
innodb_log_files_in_group got value 2
innodb_log_file_size got value 681574400

Segmentation fault (core dumped)

(gdb) bt
#0  0x00002ba9d4cf1dfd in getenv () from /lib64/libc.so.6
#1  0x00002ba9d4d44e97 in tzset_internal () from /lib64/libc.so.6
#2  0x00002ba9d4d457f7 in __tz_convert () from /lib64/libc.so.6
#3  0x000000000043086e in ut_print_timestamp (file=0x2ba9d4efa840) at innodb/ut/ut0ut.c:262
#4  0x000000000041b407 in os_file_get_last_error (report_all_errors=0) at innodb/os/os0file.c:351
#5  0x000000000041b54a in os_file_handle_error_cond_exit (name=0x0, operation=0x43d116 "read", should_exit=0)
    at innodb/os/os0file.c:422
#6  0x000000000041b737 in os_file_handle_error_no_exit (name=0x0, operation=0x43d116 "read") at innodb/os/os0file.c:513
#7  0x000000000041c8bd in os_file_read_no_error_handling (file=3, buf=0x7fffd6114000, offset=32, offset_high=0,
    n=4294967295) at innodb/os/os0file.c:2485
#8  0x00000000004032e1 in get_tablespace_id (pathname=0x54c0a8 "/data0/meb/2010-11-24_02-02-33/dbt2w50/district.ibd",
    is_differential=1, space_id=0x7fffd611ae50, zip_size=0x7fffd611ae58) at back0back.c:1285
#9  0x0000000000000000 in ?? ()

How to repeat:
See description
[12 Oct 2011 18:37] Sveta Smirnova
Fixed in version 3.6.0