xtrabackup encounters fatal error trying to create temp table
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Fix Released
|
Medium
|
Alexey Kopytov | ||
2.0 |
Won't Fix
|
Medium
|
Unassigned | ||
2.1 |
Fix Released
|
Medium
|
Alexey Kopytov |
Bug Description
xtrabackup 1.6-amd64 on Solaris encounters an error during --apply-log-only when attempting to create a temporary table file, causing apply-log to fail.
I think this is a dupe of bug 402884 which is supposed to be fixed long ago, but it doesn't seem to look that way in the build I am using??
Bug Link:
https:/
Command Run:
xtrabackup --defaults-
Output:
xtrabackup: cd to /backup/
xtrabackup: This target seems to be not prepared yet.
xtrabackup: Temporary instance for recovery is set as followings.
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: Starting InnoDB instance for recovery.
xtrabackup: Using 1073741824 bytes for buffer pool (set by --use-memory parameter)
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.3
InnoDB: Warning: innodb_
110826 12:59:37 InnoDB: Initializing buffer pool, size = 1.0G
110826 12:59:38 InnoDB: Completed initialization of buffer pool
110826 12:59:38 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 5157631495386
110826 12:59:38 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Doing recovery: scanned up to log sequence number 5157636738048 (0 )
..<snip>..
InnoDB: Doing recovery: scanned up to log sequence number 5161464040448 (5 )
InnoDB: Doing recovery: scanned up to log sequence number 5161469283328 (5 )
InnoDB: Doing recovery: scanned up to log sequence number 5161474526208 (5 )
InnoDB: Doing recovery: scanned up to log sequence number 5161479769088 (5 )
110826 14:05:59 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
InnoDB: File name .//mysqldb/
InnoDB: File operation call: 'create'.
InnoDB: Cannot continue operation.
xtrabackup Ver undefined Rev undefined for 5.1.55 pc-solaris2.11 (i386)
xtrabackup: xtrabackup_logfile detected: size=75174641664, start_lsn=
Related branches
- Laurynas Biveinis (community): Approve
-
Diff: 4471 lines (+762/-724)12 files modifiedMakefile (+9/-39)
patches/innodb51.patch (+87/-88)
patches/innodb55.patch (+99/-92)
patches/innodb56.patch (+70/-67)
patches/xtradb51.patch (+114/-119)
patches/xtradb55.patch (+238/-228)
src/Makefile (+1/-1)
src/compact.cc (+1/-1)
src/innodb_int.cc (+58/-2)
src/innodb_int.h (+52/-2)
src/xtrabackup.cc (+8/-12)
utils/build.sh (+25/-73)
Changed in percona-xtrabackup: | |
assignee: | nobody → Valentine Gostev (longbow) |
tags: | added: cr i18257 |
Changed in percona-xtrabackup: | |
importance: | Undecided → High |
Changed in percona-xtrabackup: | |
assignee: | Valentine Gostev (longbow) → nobody |
Changed in percona-xtrabackup: | |
importance: | High → Undecided |
tags: | removed: cr i18257 |
To me it looks like a duplicate/ regression of bug #402884 since the os0file.c fix to change os_file_ handle_ error to os_file_ handle_ error_no_ exit appears to be missing from current xtrabackup.