安徽数据库异常分析

zhgc

现象：能正常启动，但一段时间后会停止服务

230116 13:59:51  InnoDB: Operating system error number 1117 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/ ... em-error-codes.html
InnoDB: File name .\sfc\r_unique_data_t.ibd
InnoDB: File operation call: 'Windows aio'.
InnoDB: Cannot continue operation.


先做磁盘检查：


但并没有找到错误：


再次重启mysql的记录：
230117 11:34:41 [Note] Plugin 'FEDERATED' is disabled.
230117 11:34:41  InnoDB: Initializing buffer pool, size = 2.0G
230117 11:34:42  InnoDB: Completed initialization of buffer pool
InnoDB: Log scan progressed past the checkpoint lsn 182 2337036213
230117 11:34:42  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 182 2342278656
InnoDB: Doing recovery: scanned up to log sequence number 182 2347521536
InnoDB: Doing recovery: scanned up to log sequence number 182 2352764416
InnoDB: Doing recovery: scanned up to log sequence number 182 2358007296
InnoDB: Doing recovery: scanned up to log sequence number 182 2363250176
InnoDB: Doing recovery: scanned up to log sequence number 182 2368493056
InnoDB: Doing recovery: scanned up to log sequence number 182 2373735936
InnoDB: Doing recovery: scanned up to log sequence number 182 2378978816
InnoDB: Doing recovery: scanned up to log sequence number 182 2384221696
InnoDB: Doing recovery: scanned up to log sequence number 182 2389464576
InnoDB: Doing recovery: scanned up to log sequence number 182 2394707456
InnoDB: Doing recovery: scanned up to log sequence number 182 2399950336
InnoDB: Doing recovery: scanned up to log sequence number 182 2405193216
InnoDB: Doing recovery: scanned up to log sequence number 182 2410436096
InnoDB: Doing recovery: scanned up to log sequence number 182 2415678976
InnoDB: Doing recovery: scanned up to log sequence number 182 2420921856
InnoDB: Doing recovery: scanned up to log sequence number 182 2426164736
InnoDB: Doing recovery: scanned up to log sequence number 182 2431407616
InnoDB: Doing recovery: scanned up to log sequence number 182 2436650496
InnoDB: Doing recovery: scanned up to log sequence number 182 2441893376
InnoDB: Doing recovery: scanned up to log sequence number 182 2447136256
InnoDB: Doing recovery: scanned up to log sequence number 182 2452379136
InnoDB: Doing recovery: scanned up to log sequence number 182 2457622016
InnoDB: Doing recovery: scanned up to log sequence number 182 2462864896
InnoDB: Doing recovery: scanned up to log sequence number 182 2468107776
InnoDB: Doing recovery: scanned up to log sequence number 182 2471380907
230117 11:35:00  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
InnoDB: Last MySQL binlog file position 0 106, file name D:\Mysql-binlog\mysql-bin.000022
230117 11:35:14  InnoDB: Started; log sequence number 182 2471380907
230117 11:35:14 [Note] Recovering after a crash using D:\Mysql-binlog\mysql-bin
230117 11:35:14 [Note] Starting crash recovery...
230117 11:35:14 [Note] Crash recovery finished.
230117 11:35:14 [Warning] 'user' entry 'ate_input@%;' ignored in --skip-name-resolve mode.
230117 11:35:15 [Warning] 'tables_priv' entry 'c_group_config_t ate_input@%;' ignored in --skip-name-resolve mode.
230117 11:35:15 [Warning] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--relay-log=MES-SERVER-relay-bin' to avoid this problem.
230117 11:35:15 [Note] Slave I/O thread: connected to master 'repl@192.168.22.252:3306',replication started in log 'mysql-bin.010913' at position 47805627
230117 11:35:15 [Note] Slave SQL thread initialized, starting replication in log 'mysql-bin.010907' at position 11858763, relay log '.\MES-SERVER-relay-bin.001117' position: 11858908
230117 11:35:15 [Note] Event Scheduler: Loaded 0 events
230117 11:35:15 [Note] Event Scheduler: scheduler thread started with id 3
230117 11:35:15 [Note] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld: ready for connections.
Version: '5.1.72-community-log'  socket: ''  port: 3306  MySQL Community Server (GPL)