Comment 9 for bug 1206309

Hey Guys, I hit the same bug streaming a backup between hosts. This is a 2TB dataset while I have the following configurations:

show engine innodb status\G select sleep(60); show engine innodb status\G
Log sequence number 170922005531445
1 row in set (0.00 sec)

1 row in set (1 min 0.00 sec)

Log sequence number 170922297590865
1 row in set (0.00 sec)

select round((170922297590865-170922005531445) / 1024 / 1024) as MB_per_minute;
+---------------+
| MB_per_minute |
+---------------+
| 279 |
+---------------+
1 row in set (0.00 sec)

select round(((170922297590865-170922005531445) / 1024 / 1024)*60) as MB_per_minute_per_hour;
+------------------------+
| MB_per_minute_per_hour |
+------------------------+
| 16712 |
+------------------------+
1 row in set (0.00 sec)

So, I have a little bit more than a file per hour, considering the below configuration.

select @@innodb_log_files_in_group, (@@innodb_log_file_size/1024/1024/1024) innodb_log_file_size, @@innodb_log_group_home_dir\G
*************************** 1. row ***************************
@@innodb_log_files_in_group: 2
innodb_log_file_size: 2.000000000000
@@innodb_log_group_home_dir: ./
1 row in set (0.00 sec)

So, the error on the xtrabackup output logs is:

xtrabackup: warning: Log block checksum mismatch (block no 688905413 at lsn 170777021876224):
expected 502359217, calculated checksum 192256968
xtrabackup: warning: this is possible when the log block has not been fully written by the server, will retry later.
160204 15:16:38 >> log scanned up to (170777021876224)
160204 15:16:39 >> log scanned up to (170777025428745)
160204 15:16:40 >> log scanned up to (170777028525963)

Why does that mismatch occurs?

xtrabackup: warning: Log block checksum mismatch (block no 688905413 at lsn 170777021876224):
expected 502359217, calculated checksum 192256968

This answer is not that completely clear to me yet:
https://bugs.launchpad.net/percona-xtrabackup/+bug/1206309/comments/3

Any additional advice here?