MySQL 8.0.35 crashes

[Praveen Kumar B A]

Hi All

The application is performing a read query but the database is crashing and not recovering. The force_innodb_recovery flag has to be set to 2 inorder to recover. The operating system has enough disk space. Here is the stack trace for the crash. Is there a way to identify the root cause for this crash?

2024-02-20T15:44:17.070850+01:00 3021 [Warning] [MY-012638] [InnoDB] Retry attempts for writing partial data failed.
2024-02-20T15:44:17.072376+01:00 3021 [ERROR] [MY-012639] [InnoDB] Write to file .\#innodb_temp\temp_9.ibt failed at offset 3423600640, 1048576 bytes should have been written, only 0 were written. Operating system error number 33. Check that your OS and file system support files of this size. Check also that the disk is not full or a disk quota exceeded.
2024-02-20T15:44:17.074315+01:00 3021 [ERROR] [MY-012640] [InnoDB] Error number 33 means 'Domain error'
2024-02-20T15:44:17.075637+01:00 3021 [Warning] [MY-012145] [InnoDB] Error while writing 4194304 zeroes to .\#innodb_temp\temp_9.ibt starting at offset 3422552064
2024-02-20T15:44:17.076548+01:00 3021 [ERROR] [MY-013132] [Server] The table 'C:\Windows\SERVIC~1\NETWOR~1\AppData\Local\Temp\#sql100c_bcd_38' is full!
2024-02-20T15:44:17.124983+01:00 3022 [Warning] [MY-012638] [InnoDB] Retry attempts for writing partial data failed.
2024-02-20T15:44:17.125847+01:00 3022 [Warning] [MY-012145] [InnoDB] Error while writing 4194304 zeroes to .\#innodb_temp\temp_8.ibt starting at offset 801112064
2024-02-20T15:44:17.126754+01:00 3022 [ERROR] [MY-013132] [Server] The table 'C:\Windows\SERVIC~1\NETWOR~1\AppData\Local\Temp\#sql100c_bce_38' is full!
2024-02-20T15:44:21.229098+01:00 3017 [ERROR] [MY-000035] [Server] Disk is full writing '.\redacted-bin.000021' (OS errno 28 - No space left on device). Waiting for someone to free space... Retry in 60 secs. Message reprinted in 600 secs.
2024-02-20T15:44:51.256533+01:00 3028 [Warning] [MY-013360] [Server] Plugin mysql_native_password reported: ''mysql_native_password' is deprecated and will be removed in a future release. Please use caching_sha2_password instead'
2024-02-20T15:44:51.585328+01:00 3017 [ERROR] [MY-010907] [Server] Error writing file 'redacted-bin' (errno: 28 - No space left on device)
2024-02-20T15:44:51.586284+01:00 3017 [ERROR] [MY-011072] [Server] Binary logging not possible. Message: An error occurred during flush stage of the commit. 'binlog_error_action' is set to 'ABORT_SERVER'. Server is being stopped..
2024-02-20T14:44:51Z UTC - mysqld got exception 0x16 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
Thread pointer: 0x27152f3f0d0
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...
7ff75f53c388 mysqld.exe!?my_print_stacktrace@@YAXPEBEK@Z()
7ff75e6af461 mysqld.exe!?print_fatal_signal@@YAXH@Z()
7ff75e6af1a3 mysqld.exe!?my_server_abort@@YAXXZ()
7ff75f5209aa mysqld.exe!?my_abort@@YAXXZ()
7ff75f2dc95c mysqld.exe!?ending_trans@@YA_NPEAVTHD@@_N@Z()
7ff75f2df285 mysqld.exe!?handle_binlog_flush_or_sync_error@MYSQL_BIN_LOG@@AEAAXPEAVTHD@@_NPEBD@Z()
7ff75f2e522d mysqld.exe!?ordered_commit@MYSQL_BIN_LOG@@AEAAHPEAVTHD@@_N1@Z()
7ff75f2daba1 mysqld.exe!?commit@MYSQL_BIN_LOG@@UEAA?AW4enum_result@TC_LOG@@PEAVTHD@@_N@Z()
7ff75e475092 mysqld.exe!?ha_commit_trans@@YAHPEAVTHD@@_N1@Z()
7ff75e6a4b06 mysqld.exe!?trans_commit@@YA_NPEAVTHD@@_N@Z()
7ff75e66740f mysqld.exe!?mysql_execute_command@@YAHPEAVTHD@@_N@Z()
7ff75e6629bf mysqld.exe!?dispatch_sql_command@@YAXPEAVTHD@@PEAVParser_state@@@Z()
7ff75e6615ba mysqld.exe!?dispatch_command@@YA_NPEAVTHD@@PEBTCOM_DATA@@W4enum_server_command@@@Z()
7ff75e662d76 mysqld.exe!?do_command@@YA_NPEAVTHD@@@Z()
7ff75e469bf8 mysqld.exe!?thread_id@THD@@QEBAIXZ()
7ff75fabf189 mysqld.exe!?my_init_dynamic_array@@YA_NPEAUDYNAMIC_ARRAY@@IIPEAXII@Z()
7ff75f52cb7c mysqld.exe!?my_thread_self_setname@@YAXPEBD@Z()
7ffc77cc6b4c ucrtbase.dll!_recalloc()
7ffc79344cb0 KERNEL32.DLL!BaseThreadInitThunk()
7ffc7a2ce8ab ntdll.dll!RtlUserThreadStart()

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (27189bb00f0): COMMIT
Connection ID (thread ID): 3017
Status: KILL_CONNECTION