← Back to branch summary

~sergei.glushchenko/percona-xtrabackup/test976945

« back to all changes in this revision

Viewing changes to test/t/bug976945.sh

  • Committer: Sergei Glushchenko
  • Date: 2012-06-14 07:51:10 UTC
  • Revision ID: sergei.glushchenko@percona.com-20120614075110-tcvwfkjapu3b110q
Bug976945: innodb_log_block_size=4096 is not supported
When called with --prepare xtrabackup didn't initialize
log_block_size properly.
Solution is to initialize log_block_size from inside
xtrabackup_init_temp_log when --prepare called.

Show diffs side-by-side

added added

removed removed

Lines of Context:
test/t/bug976945.sh
 
1
############################################################################
 
2
# Bug #976945: innodb_log_block_size=4096 is not supported
 
3
############################################################################
 
4
. inc/common.sh
 
5
 
 
6
 
 
7
if [ -z "$XTRADB_VERSION" ]; then
 
8
    echo "Requires XtraDB" > $SKIPPED_REASON
 
9
    exit $SKIPPED_EXIT_CODE
 
10
fi
 
11
 
 
12
init
 
13
echo innodb_log_block_size=4096 >> $topdir/my.cnf
 
14
run_mysqld --innodb_log_block_size=4096
 
15
load_sakila
 
16
 
 
17
# Full backup
 
18
# backup root directory
 
19
vlog "Starting backup"
 
20
 
 
21
full_backup_dir=$topdir/full_backup
 
22
innobackupex  --no-timestamp $full_backup_dir
 
23
 
 
24
vlog "Preparing backup"
 
25
innobackupex --apply-log --redo-only $full_backup_dir
 
26
vlog "Log applied to full backup"
 
27
 
 
28
# Destroying mysql data
 
29
stop_mysqld
 
30
rm -rf $mysql_datadir/*
 
31
vlog "Data destroyed"
 
32
 
 
33
# Restore backup
 
34
vlog "Copying files to their original locations"
 
35
innobackupex --copy-back $full_backup_dir
 
36
vlog "Data restored"
 
37
 
 
38
run_mysqld --innodb_log_block_size=4096