Bug #114608 [InnoDB] [FATAL]

Description:
2024-04-10T09:41:18.903662Z 0 [ERROR] [MY-013622] [InnoDB] [FATAL] fsync() returned EIO, aborting.
2024-04-10T09:41:18.903785Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: os0file.cc:2863:ib::fatal triggered thread 140466547078720
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/8.0/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
2024-04-10T09:41:18Z UTC - mysqld got signal 6 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
BuildID[sha1]=4ed6a3fb90a9cca143fabf01d2e55861e8963606
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 0x100000
/usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x41) [0x55841c83a781]
/usr/sbin/mysqld(print_fatal_signal(int)+0x3bc) [0x55841be4662c]
/usr/sbin/mysqld(my_server_abort()+0x7e) [0x55841be4675e]
/usr/sbin/mysqld(my_abort()+0xe) [0x55841c82f24e]
/usr/sbin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x183) [0x55841ca0c4b3]
/usr/sbin/mysqld(+0x190b016) [0x55841ca26016]
/usr/sbin/mysqld(+0x1827fc6) [0x55841c942fc6]
/usr/sbin/mysqld(os_file_flush_func(int)+0x28) [0x55841c952c28]
/usr/sbin/mysqld(Fil_shard::space_flush(unsigned int)+0x47d) [0x55841cb0855d]
/usr/sbin/mysqld(Fil_shard::flush_file_spaces()+0x155) [0x55841cb08905]
/usr/sbin/mysqld(buf_flush_do_batch(buf_pool_t*, buf_flush_t, unsigned long, unsigned long, unsigned long*)+0x274) [0x55841ca79f74]
/usr/sbin/mysqld(+0x195fe52) [0x55841ca7ae52]
/usr/sbin/mysqld(+0x1961385) [0x55841ca7c385]
/usr/sbin/mysqld(+0x180a4c5) [0x55841c9254c5]
/lib/x86_64-linux-gnu/libstdc++.so.6(+0xdc253) [0x7fcba282f253]
/lib/x86_64-linux-gnu/libc.so.6(+0x94ac3) [0x7fcba24b7ac3]
/lib/x86_64-linux-gnu/libc.so.6(+0x126850) [0x7fcba2549850]
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.
2024-04-10T09:41:22.481550Z 0 [Warning] [MY-011070] [Server] 'binlog_format' is deprecated and will be removed in a future release.
2024-04-10T09:41:22.487345Z 0 [Warning] [MY-010101] [Server] Insecure configuration for --secure-file-priv: Location is accessible to all OS users. Consider choosing a different directory.
2024-04-10T09:41:22.487405Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.36) starting as process 1003365
2024-04-10T09:41:22.517487Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2024-04-10T09:44:14.351435Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2024-04-10T09:44:17.365511Z 0 [ERROR] [MY-013180] [Server] Function 'clone' already exists.
2024-04-10T09:44:17.365562Z 0 [Warning] [MY-010736] [Server] Couldn't load plugin named 'clone' with soname 'mysql_clone.so'.
2024-04-10T09:44:18.502428Z 0 [System] [MY-010229] [Server] Starting XA crash recovery...
2024-04-10T09:44:18.519701Z 0 [System] [MY-010232] [Server] XA crash recovery finished.
2024-04-10T09:44:18.826121Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2024-04-10T09:44:18.828779Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.
2024-04-10T09:44:19.038841Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.0.36'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  MySQL Community Server - GPL.

How to repeat:
?

Suggested fix:
?

Hi Mr. Briggs,

Thank you for your bug report.

However, this is actually a duplicate of the already verified bug:

https://bugs.mysql.com/bug.php?id=114399

This bug is a private bug, so you cannot read it.

It is not a bug in our code, but in the settings. 

The workaround for your is quite easy ..... 

Just add this setting to your my.cnf:

innodb_use_fdatasync=OFF

Duplicate.