Prevent taking backups using TokuBackup if innodb_use_native_aio is enabled on server

[Shahriyar Rzayev]

As Documentation https://www.percona.com/doc/percona-tokudb/faq.html#backup states about innodb_use_native_aio it should be disabled before taking backup of InnoDB tables.

But in fact real problem is here about recovering.
The user will be able to take backups even, innodb_use_native_aio is enabled. But this backup will be unrecoverable:

2015-12-01 12:17:03 7f4ad3bff700 InnoDB: Error: page 32769 log sequence number 3773058397
InnoDB: is in the future! Current system log sequence number 3130901600.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2015-12-01 12:17:03 7f4ad3bff700 InnoDB: Error: page 49153 log sequence number 3791411962
InnoDB: is in the future! Current system log sequence number 3130901600.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
InnoDB: Page directory corruption: infimum not pointed to
2015-12-01 12:17:03 7f4ad3bff700 InnoDB: Page dump in ascii and hex (16384 bytes):
 len 16384; hex 000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2015-12-01 12:17:04 7f4ad3bff700 InnoDB: uncompressed page, stored checksum in field1 0, calculated checksums for field1: crc32 536728786, innodb 1575996416, none 3735928559, stored checksum in field2 0, calculated checksums for field2: crc32 536728786, innodb 1371122432, none 3735928559, page LSN 0 0, low 4 bytes of LSN at page end 0, page number (if stored to page already) 0, space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be a freshly allocated page
2015-12-01 12:17:04 7f4ad3bff700 InnoDB: Assertion failure in thread 139959356880640 in file rem0rec.cc line 577
/usr/sbin/mysqld(my_print_stacktrace+0x2c)[0x8d288c]
/usr/sbin/mysqld(handle_fatal_signal+0x461)[0x6578a1]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x10340)[0x7f4b73fff340]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x39)[0x7f4b73440cc9]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f4b734440d8]
/usr/sbin/mysqld[0x978a4b]
/usr/sbin/mysqld[0x95a101]
/usr/sbin/mysqld[0xa06ce2]
/usr/sbin/mysqld[0x9a87b8]
/usr/sbin/mysqld[0x9b0221]
/usr/sbin/mysqld[0xaaf749]
/usr/sbin/mysqld[0x9b0861]
/usr/sbin/mysqld[0x97485a]
/usr/sbin/mysqld[0x9d8aee]
/usr/sbin/mysqld[0x9d90cc]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8182)[0x7f4b73ff7182]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f4b7350447d]

Keeping in mind this critical situation TokuBackup should refuse taking backups if innodb_use_native_aio is enabled on server.

[George Ormond Lorch III (gl-az)]

https://tokutek.atlassian.net/browse/BACKUP-121

[Shahriyar Rzayev (rzayev-sehriyar)]

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