-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
I've seen failures recovering after a hard system crash with messages like:
2015-07-02T15:10:36.861-0400 E STORAGE [initandlisten] WiredTiger (2) [1435864236:861392][2600:0x7f6b3b048b80], file:collection-181-5805430730046625089.wt: /home/jonathan/pt-315/data/wiredTiger/collection-181-5805430730046625089.wt: No such file or directory 2015-07-02T15:10:36.861-0400 E STORAGE [initandlisten] WiredTiger (2) [1435864236:861464][2600:0x7f6b3b048b80], file:collection-181-5805430730046625089.wt: Operation failed during recovery: No such file or directory
The application is doing:
- Create a checkpoint
- Create a new table
- Write some content into the new table
Then the system crashes without flushing buffered I/O
- is depended on by
-
SERVER-19282 WiredTiger changes in MongoDB 3.1.6
- Closed
- related to
-
SERVER-19274 DB fails to recover after system crash, with "No such file or directory"
- Closed