Xtrabackup error "cannot open the destination stream for"

Bug #1017813 reported by PavelVD
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC
New
Undecided
Unassigned

Bug Description

In percona cluster during sync with xtrabackup i get such error

archive_write_header() failed.
[01] xtrabackup: error: cannot open the destination stream for ./db1/log.ibd
[01] xtrabackup: Error: xtrabackup_copy_datafile() failed.
[01] xtrabackup: Error: failed to copy datafile.
innobackupex: Error: ibbackup child process has died at /usr//bin/innobackupex line 371.

CREATE TABLE `log` (
  `user_friendly_id` int(11) NOT NULL,
  `type` varchar(64) NOT NULL,
  `file` varchar(255) NOT NULL,
  `line` smallint(6) NOT NULL,
  `code` int(11) NOT NULL,
  `message` text NOT NULL,
  `traces` text NOT NULL,
  `ts` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
  KEY `user_friendly_id` (`user_friendly_id`),
  KEY `type` (`type`),
  KEY `ts` (`ts`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8

stat of this table
*************************** 1. row ***************************
  TABLE_CATALOG: def
   TABLE_SCHEMA: db1
     TABLE_NAME: log
     TABLE_TYPE: BASE TABLE
         ENGINE: InnoDB
        VERSION: 10
     ROW_FORMAT: Compact
     TABLE_ROWS: 10087361
 AVG_ROW_LENGTH: 2331
    DATA_LENGTH: 23519559680
MAX_DATA_LENGTH: 0
   INDEX_LENGTH: 787185664
      DATA_FREE: 4194304
 AUTO_INCREMENT: NULL
    CREATE_TIME: 2012-06-25 20:39:52
    UPDATE_TIME: NULL
     CHECK_TIME: NULL
TABLE_COLLATION: utf8_general_ci
       CHECKSUM: NULL
 CREATE_OPTIONS:
  TABLE_COMMENT:

+------------------+-------+----------+----------+
| Table | Op | Msg_type | Msg_text |
+------------------+-------+----------+----------+
| db1.log | check | status | OK |
+------------------+-------+----------+----------+

Revision history for this message
Alexey Kopytov (akopytov) wrote :

It's most likely a duplucate of bug #977998 (will be fixed in XtraBackup 2.0.1). Is the log.ibd size greater than 8 GB?

I'm going to mark it as a duplicate, feel free to reopen of the problem is not fixed with XB 2.0.1.

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.