incremental crash

Bug #561106 reported by Vadim Tkachenko on 2010-04-12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraBackup moved to
Fix Released

Bug Description

I am getting crash in xtrabackup binary trying incremental

(gdb) bt
#0 0x00007ff89084d61b in memset () from /lib/
#1 0x00000000004064a0 in xtrabackup_copy_datafile (node=0x2085478) at /usr/include/bits/string3.h:96
#2 0x000000000040806f in xtrabackup_backup_func () at xtrabackup.c:3168
#3 0x000000000040a72c in main (argc=0, argv=0x2045050) at xtrabackup.c:5106

command is:

xtrabackup --backup --incremental-basedir=/data/vadim/mysqluc/2010-04-11_17-18-55 --target-dir=incremental1

Vadim Tkachenko (vadim-tk) wrote :

The problem does not appear in xtrabackup-1.1,
only exists in new binary

Changed in percona-xtrabackup:
status: New → Triaged
importance: Undecided → Critical
assignee: nobody → Yasufumi Kinoshita (yasufumi-kinoshita)
milestone: none → release-1.2
Changed in percona-xtrabackup:
milestone: 1.2 → 1.3.1
Changed in percona-xtrabackup:
milestone: 1.3.1 → 1.5
Vadim Tkachenko (vadim-tk) wrote :

Released in 1.4

Changed in percona-xtrabackup:
status: Triaged → Fix Released

Percona now uses JIRA for bug reports so this bug report is migrated to:

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

Other bug subscribers