[ERROR] InnoDB: Failed to create check sector file, errno:28 Please confirm O_DIRECT is supported and remove the file ./check_sector_size if it exists.

[imranrazakhan]

I deployed mysql5.7 on openshift 3.11 and all of sudden start getting subjected error

Following is error trace

=> sourcing 20-validate-variables.sh ...
=> sourcing 25-validate-replication-variables.sh ...
=> sourcing 30-base-config.sh ...
---> 16:29:34     Processing basic MySQL configuration files ...
=> sourcing 60-replication-config.sh ...
=> sourcing 70-s2i-config.sh ...
---> 16:29:34     Processing additional arbitrary  MySQL configuration provided by s2i ...
=> sourcing 10-mysql57.cnf ...
=> sourcing 40-paas.cnf ...
=> sourcing 50-my-tuning.cnf ...
---> 16:29:34     Starting MySQL server with disabled networking ...
---> 16:29:34     Waiting for MySQL to start ...
2019-11-28T16:29:35.049135Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2019-11-28T16:29:35.049246Z 0 [Warning] 'NO_AUTO_CREATE_USER' sql mode was not set.
2019-11-28T16:29:35.056871Z 0 [Warning] Can't create test file /var/lib/mysql/data/db-7-j26wq.lower-test
2019-11-28T16:29:35.057183Z 0 [Note] /opt/rh/rh-mysql57/root/usr/libexec/mysqld (mysqld 5.7.24) starting as process 32 ...
2019-11-28T16:29:35.069923Z 0 [Warning] Can't create test file /var/lib/mysql/data/db-7-j26wq.lower-test
2019-11-28T16:29:35.076717Z 0 [Warning] Can't create test file /var/lib/mysql/data/db-7-j26wq.lower-test
2019-11-28T16:29:35.088452Z 0 [Note] InnoDB: PUNCH HOLE support available
2019-11-28T16:29:35.088543Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-11-28T16:29:35.088568Z 0 [Note] InnoDB: Uses event mutexes
2019-11-28T16:29:35.088583Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-11-28T16:29:35.088602Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.7
2019-11-28T16:29:35.088625Z 0 [Note] InnoDB: Using Linux native AIO
2019-11-28T16:29:35.090607Z 0 [Note] InnoDB: Number of pools: 1
2019-11-28T16:29:35.091922Z 0 [Note] InnoDB: Not using CPU crc32 instructions
2019-11-28T16:29:35.098264Z 0 [ERROR] InnoDB: Failed to create check sector file, errno:28 Please confirm O_DIRECT is supported and remove the file ./check_sector_size if it exists.
2019-11-28T16:29:35.102079Z 0 [Note] InnoDB: Initializing buffer pool, total size = 32M, instances = 1, chunk size = 32M
2019-11-28T16:29:35.110285Z 0 [Note] InnoDB: Completed initialization of buffer pool
2019-11-28T16:29:35.112929Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2019-11-28T16:29:35.149932Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2019-11-28T16:29:35.155255Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 107679883092
2019-11-28T16:29:35.304185Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 107681424492
2019-11-28T16:29:35.306577Z 0 [Note] InnoDB: Database was not shutdown normally!
2019-11-28T16:29:35.306606Z 0 [Note] InnoDB: Starting crash recovery.
2019-11-28 16:29:35 0x7fcf3bbc4700  InnoDB: Assertion failure in thread 140528037152512 in file os0file.cc line 3093
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
16:29:35 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

key_buffer_size=33554432
read_buffer_size=8388608
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1310435 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x40000
/opt/rh/rh-mysql57/root/usr/libexec/mysqld(my_print_stacktrace+0x3b)[0x555b28a4e42b]
/opt/rh/rh-mysql57/root/usr/libexec/mysqld(handle_fatal_signal+0x48b)[0x555b2831b72b]
/lib64/libpthread.so.0(+0xf5d0)[0x7fcf4ba125d0]
/lib64/libc.so.6(gsignal+0x37)[0x7fcf49b122c7]
/lib64/libc.so.6(abort+0x148)[0x7fcf49b139b8]
/opt/rh/rh-mysql57/root/usr/libexec/mysqld(+0x61bde2)[0x555b282f1de2]
/opt/rh/rh-mysql57/root/usr/libexec/mysqld(_Z18os_file_flush_funci+0x91)[0x555b28b78b21]
/opt/rh/rh-mysql57/root/usr/libexec/mysqld(_Z9fil_flushm+0x232)[0x555b28d48262]
/opt/rh/rh-mysql57/root/usr/libexec/mysqld(_Z15log_io_completeP11log_group_t+0x439)[0x555b28b53329]
/opt/rh/rh-mysql57/root/usr/libexec/mysqld(_Z12fil_aio_waitm+0x108)[0x555b28d42f98]
/opt/rh/rh-mysql57/root/usr/libexec/mysqld(io_handler_thread+0xa8)[0x555b28c32c98]
/lib64/libpthread.so.0(+0x7dd5)[0x7fcf4ba0add5]
/lib64/libc.so.6(clone+0x6d)[0x7fcf49bda02d]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.