Innodb crash recovery with ALL_O_DIRECT in 5.7 errno != EINVAL

[Nickolay Ihalainen]

Split from https://bugs.launchpad.net/percona-server/+bug/1529885

Redo log reads in 5.7 are unaligned and with direct io buffers could be unaligned on OS_FILE_LOG_BLOCK_SIZE bytes.

OS_FILE_LOG_BLOCK_SIZE is defined as 512 and this problem is not directly related to unaligned 4k writes issue in original bug report.

[Nickolay Ihalainen (ihanick)]

Minimal test case:

--source include/not_windows.inc
--source include/have_innodb.inc

--disable_warnings
DROP TABLE IF EXISTS t1;
--enable_warnings

CREATE TABLE t1 (a INT, b BLOB) ENGINE=InnoDB;

INSERT INTO t1 VALUES (1, REPEAT("a", 20000));

--source include/shutdown_mysqld.inc
--let $restart_parameters=restart:--innodb-flush-method=ALL_O_DIRECT
--source include/start_mysqld.inc

[Laurynas Biveinis (laurynas-biveinis)]

https://github.com/percona/percona-server/pull/482

[Shahriyar Rzayev (rzayev-sehriyar)]

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