Comment 6 for bug 1055547

New machine same issue :

121211 13:33:31 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
InnoDB: Last MySQL binlog file position 0 678533168, file name logs/binlogs/dbOffice1-bin.000004
121211 13:33:32 InnoDB: Waiting for the background threads to start
121211 13:33:33 Percona XtraDB (http://www.percona.com) 1.1.8-20.1 started; log sequence number 193351509856

[notice (again)]
  If you use binary log and don't use any hack of group commit,
  the binary log position seems to be:
InnoDB: Last MySQL binlog file position 0 678533168, file name logs/binlogs/dbOffice1-bin.000004

xtrabackup: starting shutdown with innodb_fast_shutdown = 1
121211 13:33:38 InnoDB: Starting shutdown...
121211 13:33:42 InnoDB: Shutdown completed; log sequence number 193351515201
InnoDB: Error: tried to read 2048 bytes at offset 0 0.
InnoDB: Was only able to read 0.
121211 13:33:42 InnoDB: Operating system error number 22 in a file operation.
InnoDB: Error number 22 means 'Invalid argument'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html
InnoDB: File operation call: 'read'.
InnoDB: Cannot continue operation.
innobackupex: Error:
innobackupex: ibbackup failed at /usr//bin/innobackupex line 378.