Comment 0 for bug 382742

Hello,

if i specify a absolute path to a innodb data file, the file is not where is would expect it, when i use the --stream option...

cmd: ./innobackupex-1.5.1 --slave-info --stream=tar /mysql/backup |gzip -c >/mysql/backup/current.tar.gz

my.cnf:
innodb_data_home_dir = /
innodb_data_file_path = /mysql/data/ibdata1:128M:autoextend

If i use these parameters to make a tar stream, the result looks like this:

/mysql/backup/ (after extracting):
backup-my.cnf
mysql/data/ibdata1
mysql/columns_priv.frm
mysql/db.frm
...

> xtrabackup: cd to /mysql/data
> xtrabackup: Target instance is assumed as followings.
> xtrabackup: innodb_data_home_dir = /
> xtrabackup: innodb_data_file_path = /mysql/data/ibdata1:128M:autoextend
> xtrabackup: innodb_log_group_home_dir = /mysql/logs
> xtrabackup: innodb_log_files_in_group = 2
> xtrabackup: innodb_log_file_size = 134217728
> xtrabackup: use O_DIRECT
> xtrabackup: Stream mode.
> >> log scanned up to (109 1074543189)
>
> 090602 14:36:52 innobackupex: Continuing after ibbackup has suspended
>
> innobackupex: Starting to backup InnoDB tables and indexes
> innobackupex: from original InnoDB data directory '/'
> innobackupex: Backing up as tar stream '/mysql/data/ibdata1'

If i change the parameters in the my.cnf to:
innodb_data_home_dir = /mysql/logs
innodb_data_file_path = ibdata1:128M:autoextend

> xtrabackup: cd to /mysql/data
> xtrabackup: Target instance is assumed as followings.
> xtrabackup: innodb_data_home_dir = /mysql/data
> xtrabackup: innodb_data_file_path = ibdata1:128M:autoextend
> xtrabackup: innodb_log_group_home_dir = /mysql/logs
> xtrabackup: innodb_log_files_in_group = 2
> xtrabackup: innodb_log_file_size = 134217728
> xtrabackup: use O_DIRECT
> xtrabackup: Stream mode.

/mysql/backup/ (after extracting):
backup-my.cnf
ibdata1
mysql/columns_priv.frm
mysql/db.frm
....

(as expected).

I guess, it might be related to tar converting absolute pathnames to relatives.

Greets
MarkD