Innodb crash recovery with ALL_O_DIRECT in 5.7 errno != EINVAL
Bug #1578516 reported by
Nickolay Ihalainen
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS | Status tracked in 5.7 | |||||
5.5 |
Invalid
|
Undecided
|
Unassigned | |||
5.6 |
Invalid
|
Undecided
|
Unassigned | |||
5.7 |
Fix Released
|
High
|
Nickolay Ihalainen |
Bug Description
Split from https:/
Redo log reads in 5.7 are unaligned and with direct io buffers could be unaligned on OS_FILE_
OS_FILE_
Minimal test case:
--source include/ not_windows. inc have_innodb. inc
--source include/
--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 parameters= restart: --innodb- flush-method= ALL_O_DIRECT start_mysqld. inc
--let $restart_
--source include/