xtrabackup 1.2-22 RHEL5 fails

Bug #568087 reported by Craig Van Tassle
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Percona XtraBackup moved to https://jira.percona.com/projects/PXB
Fix Released
Undecided
Aleksandr Kuzminsky
Nominated for Trunk by Jay Prall

Bug Description

I'm running the rpm for 1.2-22 RHEL5.
I do a backup and goes though and backups quite a bit of data, then on the same table it always fails with this error.
100421 15:23:58 InnoDB: Operating system error number 9 in a file operation.
InnoDB: Error number 9 means 'Bad file descriptor'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/operating-system-error-codes.html
InnoDB: File operation call: 'close'.
InnoDB: Cannot continue operation.

Changed in percona-xtrabackup:
assignee: nobody → Aleksandr Kuzminsky (akuzminsky)
Revision history for this message
konrad rzentarzewski (kondi) wrote :

same here...

100428 13:57:52 InnoDB: Operating system error number 9 in a file operation.
InnoDB: Error number 9 means 'Bad file descriptor'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/operating-system-error-codes.html
InnoDB: File operation call: 'close'.
InnoDB: Cannot continue operation.
innobackupex-1.5.1: Error: ibbackup child process has died at /usr/bin/innobackupex-1.5.1 line 479.

relevant my.cnf entries:
innodb_file_per_table = 1
innodb_additional_mem_pool_size = 16M
innodb_buffer_pool_size = 1536M
innodb_data_file_path = ibdata10:10M:autoextend
innodb_file_io_threads = 4
innodb_thread_concurrency = 4
innodb_flush_log_at_trx_commit = 0
innodb_log_buffer_size = 8M
innodb_log_file_size = 128M
innodb_log_files_in_group = 3
innodb_max_dirty_pages_pct = 90
innodb_lock_wait_timeout = 120
innodb_flush_method = O_DIRECT

rpms:
Name : xtrabackup Relocations: (not relocatable)
Version : 1.2 Vendor: (none)
Release : 14.rhel5 Build Date: Sun 11 Apr 2010 05:16:52 PM CEST
Install Date: Fri 23 Apr 2010 07:00:28 PM CEST Build Host: CentOS-5-i386.buildbot.percona.com
Group : Server/Databases Source RPM: xtrabackup-1.2-14.rhel5.src.rpm
Size : 2788427 License: GPLv2
Signature : DSA/SHA1, Tue 13 Apr 2010 05:48:32 PM CEST, Key ID 1c4cbdcdcd2efd2a
Packager : Vadim Tkachenko <email address hidden>
URL : http://percona.com/percona-lab.html
Summary : XtraBackup online backup for MySQL / InnoDB
Description :
Percona XtraBackup is OpenSource online (non-blockable) backup solution for InnoDB and XtraDB engines.

red hat:
CentOS release 5.4 (Final)

uname:
Linux blade103.non.3dart.com 2.6.18-164.6.1.el5 #1 SMP Tue Nov 3 16:18:27 EST 2009 i686 i686 i386 GNU/Linux

call:
innobackupex-1.5.1 --user root --password *** /mnt/

Revision history for this message
goto (gotolaunchpad) wrote :

Checkout the lastest code from the repos, appears to have been fixed:

http://groups.google.com/group/percona-dev/browse_thread/thread/93b2a1b4abfb517d

Revision history for this message
konrad rzentarzewski (kondi) wrote :

yes, not it's ok.

100504 01:01:08 innobackupex-1.5.1: completed OK!

Revision history for this message
konrad rzentarzewski (kondi) wrote :

s/not/now/

Revision history for this message
Yasufumi Kinoshita (yasufumi-kinoshita) wrote :

Sorry, I forgot to treat this bug...

Changed in percona-xtrabackup:
status: New → Fix Committed
Revision history for this message
Craig Van Tassle (cvantassle) wrote :

This bug appears to be fixed. I'm running a couple of test backups and restores.

Revision history for this message
Jay Prall (j4y) wrote :

I'm also having this same issue running on CentOS 5.4 in xen. I'm having trouble building the trunk version of xtrabackup in mysql-5.1.42 source as well. Any information to get me past this issue is appreciated.

Revision history for this message
cclark (cclark) wrote :

Is there a 1.2-23.rhel5 RPM in the works to address this bug or are you suggesting users just build by hand?

We have minimal RPM knowledge and given the spec file on the site I think we could build the artifact but if you have an automated build process we'd prefer to stick to the certified builds Percona provides.

thanks,

Revision history for this message
Vide (vide80) wrote :

Hi

I have xtrabckup 1.2-132.5.0.3.16 installed from DEB on Debian Lenny 5.0.4 amd64 and I'm seeing this error as well. I wonder if this bug should be already fixed in my version or not. The mysql server is a 5.1.44

Revision history for this message
Vide (vide80) wrote :

Cool, I guess that the -132 in my version number is the bazaar revision, and that your bugfix[1] is in revision 133... I'm a lucky guy :)

[1] http://www.percona.com/downloads/XtraBackup/XtraBackup-1.2/Linux/binary/x86_64/xtrabackup-1.2.tar.gz

Revision history for this message
Vide (vide80) wrote :
Revision history for this message
Vide (vide80) wrote :

Ok, compiled manually xtrabackup revision 133 against Percona Server 10.2 and now it works.

cclark, it's just one file, you can just install the old RPM and then replace the executable

Changed in percona-xtrabackup:
milestone: none → 1.2
status: Fix Committed → Fix Released
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

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

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.