innodb_data_file_path is handled by innobackupex incorrectly
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Fix Released
|
Low
|
Sergei Glushchenko | ||
2.0 |
Fix Released
|
Low
|
Sergei Glushchenko | ||
2.1 |
Fix Released
|
Low
|
Sergei Glushchenko |
Bug Description
Test case:
#######
# This testcase demonstrates incorrect handling of innodb-
# innobackupex script
#######
. inc/common.sh
cheaty_
start_server --innodb-
echo "innodb-
${MYSQL} ${MYSQL_ARGS} test <<EOF
create table test_table (a int) engine=MyISAM;
insert into test_table values (100);
EOF
backup_
innobackupex --no-timestamp $backup_dir
vlog "Backup created in directory $backup_dir"
stop_server
rm -rf $mysql_datadir/*
vlog "Data destroyed"
innobackupex --copy-back $backup_dir
start_server
# Following will fail if bug is present
${MYSQL} ${MYSQL_ARGS} test <<EOF
select * from test_table;
EOF
Is failing with message:
ERROR 29 (HY000) at line 1: File './test/
Related branches
- Alexey Kopytov (community): Approve
- George Ormond Lorch III (community): Approve (g2)
-
Diff: 717 lines (+373/-100)3 files modifiedinnobackupex (+96/-37)
src/xtrabackup.cc (+157/-63)
test/t/bug856400.sh (+120/-0)
- Alexey Kopytov (community): Approve
- George Ormond Lorch III (community): Approve (g2)
-
Diff: 726 lines (+378/-102)3 files modifiedinnobackupex (+96/-37)
src/xtrabackup.cc (+162/-65)
test/t/bug856400.sh (+120/-0)
summary: |
- innodb_data_file_path if handled by innobackupex incorrectly + innodb_data_file_path is handled by innobackupex incorrectly |
What's exactly is the condition that triggers this bug? Is it that the system tablespace name must end with '.MYD'?