[SERVER-71116] Because of I/O device error, unable to run the request. Created: 07/Nov/22  Updated: 08/Nov/22  Resolved: 07/Nov/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: GRH FEF Assignee: Chris Kelly
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-40204 : WT_ERROR: non-specific WiredTiger e... Closed
Operating System: ALL
Steps To Reproduce:

WT_SESSION.log_flush: __win_file_sync, 375: C:\Program Files (x86)\xxx\mongodb\data\journal\WiredTigerLog.0000000003 handle-sync: FlushFileBuffers: 由于 I/O 设备错误,无法运行此项请求。
: WT_ERROR: non-specific WiredTiger error Raw: [1667750110:490114][2276:140704377298992]
WT_SESSION.log_flush: __win_file_sync, 375: C:\Program Files (x86)\xxx\mongodb\data\journal\WiredTigerLog.0000000003 handle-sync: FlushFileBuffers: 由于 I/O 设备错误,无法运行此项请求。
: WT_ERROR: non-specific WiredTiger error
2022-11-06T23:55:24.200+0800 F -        [WTJournalFlusher] Invariant failure: _waitUntilDurableSession->log_flush(_waitUntilDurableSession, "sync=on") resulted in status UnknownError: -31802: WT_ERROR: non-specific WiredTiger error at src\mongo\db\storage\wiredtiger\wiredtiger_session_cache.cpp 305
2022-11-06T23:55:24.201+0800 F -        [WTJournalFlusher] 

***aborting after invariant() failure

2022-11-06T23:55:40.910+0800 F -        [WTJournalFlusher] Got signal: 22 (SIGABRT).
mongod.exe    ...\src\mongo\util\stacktrace_windows.cpp(247)                                   mongo::printStackTrace+0x43
mongod.exe    ...\src\mongo\util\signal_handlers_synchronous.cpp(184)                          mongo::`anonymous namespace'::printSignalAndBacktrace+0x74
mongod.exe    ...\src\mongo\util\signal_handlers_synchronous.cpp(240)                          mongo::`anonymous namespace'::abruptQuit+0x85
ucrtbase.dll                                                                                   raise+0x1e8
ucrtbase.dll                                                                                   abort+0x31
mongod.exe    ...\src\mongo\util\assert_util.cpp(129)                                          mongo::invariantOKFailed+0x228
mongod.exe    ...\src\mongo\db\storage\wiredtiger\wiredtiger_session_cache.cpp(305)            mongo::WiredTigerSessionCache::waitUntilDurable+0x39a
mongod.exe    ...\src\mongo\db\storage\wiredtiger\wiredtiger_kv_engine.cpp(252)                mongo::WiredTigerKVEngine::WiredTigerJournalFlusher::run+0x29e
mongod.exe    ...\src\mongo\util\background.cpp(153)                                           mongo::BackgroundJob::jobBody+0x131
mongod.exe    c:\program files (x86)\microsoft visual studio 14.0\vc\include\thr\xthread(247)  std::_LaunchPad<std::unique_ptr<std::tuple<<lambda_8929d5e2502e4de5883694c1a7a329eb> >,std::default_delete<std::tuple<<lambda_8929d5e2502e4de5883694c1a7a329eb> > > > >::_Run+0x77
mongod.exe    c:\program files (x86)\microsoft visual studio 14.0\vc\include\thr\xthread(210)  std::_Pad::_Call_func+0x9
ucrtbase.dll                                                                                   crt_at_quick_exit+0x7d
KERNEL32.DLL                                                                                   BaseThreadInitThunk+0x22
2022-11-06T23:55:40.911+0800 F CONTROL  [WTJournalFlusher] *** unhandled exception 0x0000000E at 0x00007FF84931A1C8, terminating
2022-11-06T23:55:40.911+0800 F CONTROL  [WTJournalFlusher] *** stack trace for unhandled exception:
2022-11-06T23:55:40.940+0800 I -        [WTJournalFlusher] KERNELBASE.dll                                                                                   RaiseException+0x68
mongod.exe      ...\src\mongo\util\signal_handlers_synchronous.cpp(241)                          mongo::`anonymous namespace'::abruptQuit+0x9d
ucrtbase.dll                                                                                     raise+0x1e8
ucrtbase.dll                                                                                     abort+0x31
mongod.exe      ...\src\mongo\util\assert_util.cpp(129)                                          mongo::invariantOKFailed+0x228
mongod.exe      ...\src\mongo\db\storage\wiredtiger\wiredtiger_session_cache.cpp(305)            mongo::WiredTigerSessionCache::waitUntilDurable+0x39a
mongod.exe      ...\src\mongo\db\storage\wiredtiger\wiredtiger_kv_engine.cpp(252)                mongo::WiredTigerKVEngine::WiredTigerJournalFlusher::run+0x29e
mongod.exe      ...\src\mongo\util\background.cpp(153)                                           mongo::BackgroundJob::jobBody+0x131
mongod.exe      c:\program files (x86)\microsoft visual studio 14.0\vc\include\thr\xthread(247)  std::_LaunchPad<std::unique_ptr<std::tuple<<lambda_8929d5e2502e4de5883694c1a7a329eb> >,std::default_delete<std::tuple<<lambda_8929d5e2502e4de5883694c1a7a329eb> > > > >::_Run+0x77
mongod.exe      c:\program files (x86)\microsoft visual studio 14.0\vc\include\thr\xthread(210)  std::_Pad::_Call_func+0x9
ucrtbase.dll                                                                                     crt_at_quick_exit+0x7d
KERNEL32.DLL                                                                                     BaseThreadInitThunk+0x22
2022-11-06T23:55:40.942+0800 I CONTROL  [WTJournalFlusher] writing minidump diagnostic file C:\Program Files (x86)\xxx\mongodb\bin\mongod.2022-11-06T15-55-40.mdmp
2022-11-06T23:55:41.607+0800 F CONTROL  [WTJournalFlusher] *** immediate exit due to unhandled exception

Participants:

 Description   

Hi, using Mongod:

Version: 4.0.10

OS: windows 10 

Question:

 Running a few days, get an error:

: WT_ERROR: non-specific WiredTiger error Raw: [1667750110:490114][2276:140704377298992]
WT_SESSION.log_flush: __win_file_sync, 375: C:\Program Files (x86)\xxx\mongodb\data\journal\WiredTigerLog.0000000003 handle-sync: FlushFileBuffers: 由于 I/O 设备错误,无法运行此项请求。

 

Any ideas? Looking forward for your reply.



 Comments   
Comment by GRH FEF [ 08/Nov/22 ]

Thx.

Comment by Chris Kelly [ 07/Nov/22 ]

Hello,

This error looks like it occurred due to the WiredTiger journal being unable to correctly flush its data to disk, and it seems unclear why. Generally, this invariant has suggested disk or other system level issues in the past. You can check out SERVER-40204 which appears to be similar. You can also check out this search filter for more broad information about WiredTiger errors like this as well.

MongoDB 4.0 reached end of life in April 2022 and is no longer supported, so I'm going to go ahead and close this for now. If your issues persist on a supported version, please come back to the ticket and submit:

For each node in the replica set spanning a time period that includes the incident, an archive (tar or zip) to the ticket:

  • the mongod logs
  • the $dbpath/diagnostic.data directory (the contents are described here)

Regards,
Christopher

Generated at Thu Feb 08 06:18:05 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.