Innodb crash recovery with ALL_O_DIRECT in 5.7 errno != EINVAL

Bug #1578516 reported by Nickolay Ihalainen on 2016-05-05
8
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://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) wrote :

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

Changed in percona-server:
status: New → Confirmed
tags: added: xtradb
tags: added: 64171

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

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers