[InnoDB] Operating system error number 995 in a file operation.

2022-04-06T13:42:50.830558Z 0 [Warning] [MY-010915] [Server] ‘NO_ZERO_DATE’, ‘NO_ZERO_IN_DATE’ and ‘ERROR_FOR_DIVISION_BY_ZERO’ sql modes should be used with strict mode. They will be merged with strict mode in a future release.
2022-04-06T13:42:50.833047Z 0 [System] [MY-010116] [Server] C:\Program Files\MySQL\MySQL Server 8.0\bin\mysqld.exe (mysqld 8.0.28) starting as process 3984
2022-04-06T13:42:50.848341Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2022-04-06T13:42:53.586336Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2022-04-06T13:42:54.616563Z 0 [System] [MY-010229] [Server] Starting XA crash recovery…
2022-04-06T13:42:54.626319Z 0 [System] [MY-010232] [Server] XA crash recovery finished.
2022-04-06T13:42:55.120476Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2022-04-06T13:42:55.120718Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.
2022-04-06T13:42:55.183543Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: ‘::’ port: 33060
2022-04-06T13:42:55.183772Z 0 [System] [MY-010931] [Server] C:\Program Files\MySQL\MySQL Server 8.0\bin\mysqld.exe: ready for connections. Version: ‘8.0.28’  socket: ”  port: 3306  MySQL Community Server – GPL.
2022-04-06T13:43:12.642143Z 22 [Warning] [MY-010056] [Server] Host name ‘ecs-121-36-226-95.compute.hwclouds-dns.com’ could not be resolved: 不知道这样的主机。
2022-04-06T13:43:21.471224Z 0 [ERROR] [MY-012611] [InnoDB] Operating system error number 995 in a file operation.
2022-04-06T13:43:21.471576Z 0 [ERROR] [MY-012617] [InnoDB] The error means that the I/O operation has been aborted because of either a thread exit or an application request. Retry attempt is made.
2022-04-06T13:43:21.581172Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: os0file.cc:3776:ret || GetLastError() != ERROR_IO_PENDING thread 264
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/ … nnodb-recovery.html
InnoDB: about forcing recovery.
13:43:21 UTC – mysqld got exception 0x16 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
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…
2022-04-06T13:43:21.581769Z 0 [ERROR] [MY-012611] [InnoDB] Operating system error number 995 in a file operation.
2022-04-06T13:43:21.582029Z 0 [ERROR] [MY-012617] [InnoDB] The error means that the I/O operation has been aborted because of either a thread exit or an application request. Retry attempt is made.
7ff79652fd48    mysqld.exe!?my_print_stacktrace@@YAXPEBEK@Z()
7ff79576004b    mysqld.exe!?print_fatal_signal@@YAXH@Z()
7ff79575fe13    mysqld.exe!?my_server_abort@@YAXXZ()
7ff79651643a    mysqld.exe!?my_abort@@YAXXZ()
7ff79674c579    mysqld.exe!??$endl@DU?$char_traits@D@std@@@std@@YAAEAV?$basic_ostream@DU?$char_traits@D@std@@@0@AEAV10@@Z()
7ff79669bd51    mysqld.exe!?set_compression_level@Zstd_comp@compression@transaction@binary_log@@UEAAXI@Z()
7ff79669d5da    mysqld.exe!?set_compression_level@Zstd_comp@compression@transaction@binary_log@@UEAAXI@Z()
7ff79669c7da    mysqld.exe!?set_compression_level@Zstd_comp@compression@transaction@binary_log@@UEAAXI@Z()
7ff7966be3f4    mysqld.exe!??$endl@DU?$char_traits@D@std@@@std@@YAAEAV?$basic_ostream@DU?$char_traits@D@std@@@0@AEAV10@@Z()
7ff79670e091    mysqld.exe!??$endl@DU?$char_traits@D@std@@@std@@YAAEAV?$basic_ostream@DU?$char_traits@D@std@@@0@AEAV10@@Z()
7ff79670b7b4    mysqld.exe!??$endl@DU?$char_traits@D@std@@@std@@YAAEAV?$basic_ostream@DU?$char_traits@D@std@@@0@AEAV10@@Z()
7ffbd887f4a0    ucrtbase.DLL!_o__realloc_base()
7ffbe11f13f2    KERNEL32.DLL!BaseThreadInitThunk()
7ffbe1805504    ntdll.dll!RtlUserThreadStart()
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.
2022-04-06T13:43:21.690531Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: os0file.cc:3776:ret || GetLastError() != ERROR_IO_PENDING thread 3916
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/ … nnodb-recovery.html
InnoDB: about forcing recovery.
2022-04-06T13:43:21.690395Z 0 [ERROR] [MY-012611] [InnoDB] Operating system error number 995 in a file operation.
2022-04-06T13:43:21.740014Z 0 [ERROR] [MY-012617] [InnoDB] The error means that the I/O operation has been aborted because of either a thread exit or an application request. Retry attempt is made.
2022-04-06T13:43:21.847015Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: os0file.cc:3776:ret || GetLastError() != ERROR_IO_PENDING thread 2920
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/ … nnodb-recovery.html
InnoDB: about forcing recovery.
2022-04-06T13:43:21.847363Z 0 [ERROR] [MY-012611] [InnoDB] Operating system error number 995 in a file operation.
2022-04-06T13:43:21.847614Z 0 [ERROR] [MY-012617] [InnoDB] The error means that the I/O operation has been aborted because of either a thread exit or an application request. Retry attempt is made.
2022-04-06T13:43:21.956273Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: os0file.cc:3776:ret || GetLastError() != ERROR_IO_PENDING thread 992
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/ … nnodb-recovery.html
InnoDB: about forcing recovery.