innodb_log_file_size may be displayed incorrectly on 32-bit platforms

[Alexey Kopytov]

XtraBackup prints the value of innodb_log_file_size incorrectly on 32-bit platforms. The reason is that it is always printed as "long long signed int", but the type of srv_log_file_size in InnoDB versions < 5.6 is 'ulint', i.e. a 32-bit integer on a 32-bit platform. I don't think it has any significant impact, because:

1. It is only for 32-bit platforms.
2. The value is only printed incorrectly (but a correct value is used internally).
3. Even if an incorrect value is stored backup-my.cnf (and then read by xtrabackup later to create empty log files), it will only lead to the log files being created with a wrong size (or the second --apply-log failing with an error).

Hence the Low priority.

[Alexey Kopytov (akopytov)]

Does not apply to 2.2+ due to single binary changes.

[Shahriyar Rzayev (rzayev-sehriyar)]

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-1251