Comment 5 for bug 339013

HI Vadim,

just got the latest revno. 34 from launchpad. Began from scratch (extract, patch, build).

# /home/md/xtrabackup --backup
./xtrabackup Ver beta-0.4 for 5.1.32 unknown-linux-gnu (x86_64)
>> log scanned up to (25 733862973)
Copying //mysql/data/ibdata1
     to /mysql/backup/ibdata1
>> log scanned up to (25 734293011)
>> log scanned up to (25 734619380)
        ...done
>> log scanned up to (25 734971958)
...
The latest check point (for incremental): '25:579639574'
>> log scanned up to (25 769313172)
Stopping log copying thread.
Transaction log of lsn (25 543693125) to (25 769313172) was copied.

Now the --prepare directly fails at start:

# ./xtrabackup --prepare
./xtrabackup Ver beta-0.4 for 5.1.32 unknown-linux-gnu (x86_64)
xtrabackup: This target seems to be not prepared yet.
xtrabackup_logfile detected: size=225624064, start_lsn=(25 543693125)
xtrabackup: Starting InnoDB instance for recovery.
xtrabackup: Using 104857600 bytes for buffer pool (set by --use-memory parameter)
090403 9:48:58 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
InnoDB: File name .//mysql/data/ibdata1
InnoDB: File operation call: 'create'.
InnoDB: Cannot continue operation.

My innodb/xtrabackup config:

innodb_data_file_path = /mysql/data/ibdata1:128M:autoextend
innodb_file_per_table
innodb_log_group_home_dir = /mysql/logs
innodb_buffer_pool_size = 4096M
innodb_additional_mem_pool_size = 32M
innodb_log_file_size = 128M
innodb_log_files_in_group = 2
innodb_log_buffer_size = 16M
innodb_flush_log_at_trx_commit = 2
innodb_lock_wait_timeout = 50
innodb_thread_concurrency = 0

[xtrabackup]
target_dir = /mysql/backup