innodb_data_home_dir support is buggy (PXB 2.2 regression)

Bug #1386013 reported by Sergei Glushchenko on 2014-10-27
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraBackup moved to https://jira.percona.com/projects/PXB
Fix Released
Medium
Sergei Glushchenko
2.2
Fix Released
Medium
Sergei Glushchenko

Bug Description

Test case

. inc/common.sh

mkdir -p ${TEST_VAR_ROOT}/dir/data

MYSQLD_EXTRA_MY_CNF_OPTS="
innodb_file_per_table=1
innodb_data_home_dir=${TEST_VAR_ROOT}/dir/data
"

start_server
load_sakila

checksum1=`checksum_table sakila payment`
test -n "$checksum1" || die "Failed to checksum table sakila.payment"

innobackupex --no-timestamp $topdir/backup

stop_server

rm -rf $MYSQLD_DATADIR/*
rm -rf ${TEST_VAR_ROOT}/dir/data/*

innobackupex --apply-log $topdir/backup
innobackupex --copy-back $topdir/backup

start_server

checksum2=`checksum_table sakila payment`
test -n "$checksum2" || die "Failed to checksum table sakila.payment"

Passes in 2.1 but failed in 2.2

Alexey Kopytov (akopytov) wrote :

This is a regression from https://blueprints.launchpad.net/percona-xtrabackup/+spec/read-server-options-with-show-variables, so it did not appear in a released version. Can go to "Other bugs" in release notes.

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-711

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers