Comment 1 for bug 664128

Partha,

could you please provide more details on use case you have tried? Or what do you mean by not properly parsed?

I have tried putting this option both to xtrabackup's args and to mysql config file - have not met any troubles.

with xtrabackup 1.5:

root@dev302:~# xtrabackup --backup --target-dir=/root/backup/bbb --loose-innodb_read_io_threads
xtrabackup Ver 1.5 Rev 203 for 5.1.53 unknown-linux-gnu (x86_64)
xtrabackup: uses posix_fadvise().
xtrabackup: cd to /var/lib/mysql
xtrabackup: Target instance is assumed as followings.
xtrabackup: innodb_data_home_dir = ./
xtrabackup: innodb_data_file_path = ibdata1:10M:autoextend
xtrabackup: innodb_log_group_home_dir = ./
xtrabackup: innodb_log_files_in_group = 2
xtrabackup: innodb_log_file_size = 5242880
110221 23:04:11 InnoDB: Warning: allocated tablespace 10, old maximum was 9
>> log scanned up to (45356)
[01] Copying ./ibdata1
     to /root/backup/bbb/ibdata1
[01] ...done
[01] Copying ./test/t1.ibd
     to /root/backup/bbb/test/t1.ibd
[01] ...done
xtrabackup: The latest check point (for incremental): '45356'
>> log scanned up to (45356)
xtrabackup: Stopping log copying thread..
xtrabackup: Transaction log of lsn (45356) to (45356) was copied.
root@dev302:~#