innobackupex fails when --no-lock and --rsync are used in conjunction
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Fix Released
|
Medium
|
Sergei Glushchenko | ||
2.0 |
Fix Released
|
Medium
|
Sergei Glushchenko | ||
2.1 |
Fix Released
|
Medium
|
Sergei Glushchenko |
Bug Description
This command line will fail:
innobackupex --defaults-
kolita@lilith:~$ xtrabackup --version
xtrabackup version 2.0.5 for Percona Server 5.1.59 unknown-linux-gnu (x86_64) (revision id: undefined)
kolita@lilith:~$ innobackupex --defaults-
InnoDB Backup Utility v1.5.1-xtrabackup; Copyright 2003, 2009 Innobase Oy
and Percona Ireland Ltd 2009-2012. All Rights Reserved.
This software is published under
the GNU GENERAL PUBLIC LICENSE Version 2, June 1991.
130212 16:37:51 innobackupex: Starting mysql with options: --defaults-
130212 16:37:51 innobackupex: Connected to database with mysql child process (pid=6470)
130212 16:37:57 innobackupex: Connection to database server closed
IMPORTANT: Please check that the backup run completes successfully.
At the end of a successful backup run innobackupex
prints "completed OK!".
innobackupex: Using mysql Ver 14.14 Distrib 5.5.29, for debian-linux-gnu (x86_64) using readline 6.2
innobackupex: Using mysql server version Copyright (c) 2000, 2012, Oracle and/or its affiliates. All rights reserved.
innobackupex: Created backup directory /tmp/2013-
130212 16:37:57 innobackupex: Starting mysql with options: --defaults-
130212 16:37:57 innobackupex: Connected to database with mysql child process (pid=6498)
130212 16:37:59 innobackupex: Connection to database server closed
130212 16:37:59 innobackupex: Starting ibbackup with command: xtrabackup_55 --defaults-
innobackupex: Waiting for ibbackup (pid=6506) to suspend
innobackupex: Suspend file '/tmp/2013-
xtrabackup_55 version 2.0.5 for Percona Server 5.5.16 Linux (x86_64) (revision id: undefined)
xtrabackup: uses posix_fadvise().
xtrabackup: cd to /home/kolita/
xtrabackup: Target instance is assumed as followings.
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: using O_DIRECT
130212 16:37:59 InnoDB: Warning: allocated tablespace 28, old maximum was 9
>> log scanned up to (13418540430)
[01] Copying ./ibdata1 to /tmp/2013-
>> log scanned up to (13418540430)
[01] ...done
[01] ./test/
[01] Copying ./test/
[01] ...done
[01] Copying ./test/dt.ibd to /tmp/2013-
[01] ...done
[01] Copying ./test/i28581.ibd to /tmp/2013-
[01] ...done
[01] Copying ./test/t.ibd to /tmp/2013-
[01] ...done
[01] Copying ./test/t1.ibd to /tmp/2013-
[01] ...done
[01] Copying ./test/b.ibd to /tmp/2013-
[01] ...done
[01] Copying ./test/c.ibd to /tmp/2013-
[01] ...done
[01] Copying ./sbtest/
>> log scanned up to (13418540430)
[01] ...done
[01] Copying ./sbtest/
[01] ...done
[01] Copying ./sbtest/
[01] ...done
>> log scanned up to (13418540430)
[01] Copying ./sbtest/
[01] ...done
[01] Copying ./world/Country.ibd to /tmp/2013-
[01] ...done
[01] Copying ./world/
[01] ...done
[01] Copying ./world/City.ibd to /tmp/2013-
[01] ...done
[01] Copying ./percona/a.ibd to /tmp/2013-
[01] ...done
[01] Copying ./employees/
[01] ...done
[01] Copying ./employees/
[01] ...done
[01] Copying ./employees/
>> log scanned up to (13418540430)
[01] ...done
[01] Copying ./employees/
[01] ...done
[01] Copying ./employees/
[01] ...done
[01] Copying ./employees/
[01] ...done
>> log scanned up to (13418540430)
130212 16:38:25 innobackupex: Continuing after ibbackup has suspended
130212 16:38:25 innobackupex: Starting mysql with options: --defaults-
130212 16:38:25 innobackupex: Connected to database with mysql child process (pid=6535)
130212 16:38:27 innobackupex: Starting to backup non-InnoDB tables and files
innobackupex: in subdirectories of '/home/
innobackupex: Backing up files '/home/
innobackupex: Backing up file '/home/
innobackupex: Backing up files '/home/
innobackupex: Backing up file '/home/
innobackupex: Backing up files '/home/
innobackupex: Backing up file '/home/
innobackupex: Backing up file '/home/
innobackupex: Backing up file '/home/
innobackupex: Backing up file '/home/
innobackupex: Backing up file '/home/
innobackupex: Backing up file '/home/
innobackupex: Backing up file '/home/
innobackupex: Backing up file '/home/
innobackupex: Backing up file '/home/
innobackupex: Backing up file '/home/
innobackupex: Backing up file '/home/
innobackupex: Backing up file '/home/
innobackupex: Backing up file '/home/
innobackupex: Backing up file '/home/
innobackupex: Backing up file '/home/
innobackupex: Backing up file '/home/
innobackupex: Backing up file '/home/
innobackupex: Backing up file '/home/
innobackupex: Backing up file '/home/
innobackupex: Backing up file '/home/
# Here it does the second pass directly
130212 16:38:27 Starting rsync as: rsync -t "/home/
130212 16:38:27 rsync finished successfully.
# and when it tries to perform the cleanup of the first stage it fails because the file isn't there... seems there's no prep when --no-lock?
innobackupex: Error: Can't open /home/kolita/
kolita@lilith:~$ >> log scanned up to (13418540430)
Related branches
- Laurynas Biveinis (community): Approve
-
Diff: 42 lines (+26/-1)2 files modifiedinnobackupex (+1/-1)
test/t/ib_rsync_nolock.sh (+25/-0)
- Laurynas Biveinis (community): Approve
-
Diff: 42 lines (+26/-1)2 files modifiedinnobackupex (+1/-1)
test/t/ib_rsync_nolock.sh (+25/-0)
Right, there's no prep copy with --no-lock, we should just not attempt to delete the prep file list in this case.