[SERVER-54416] WT_SESSION.checkpoint: __wt_turtle_update, 418: WiredTiger.turtle: fatal turtle file update error: File exists Created: 09/Feb/21 Updated: 27/Oct/23 Resolved: 25/Feb/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 4.0.10 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Chris De Bruyne | Assignee: | Dmitry Agranat |
| Resolution: | Community Answered | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | ALL |
| Participants: |
| Description |
|
Hello, we are investigating what went wrong with our database but when we start the db we get the following in the logs. I'm afraid the logs before are gone so we might not be able to tell you what happend.
Any tips on how to recover our data, before we use our backup?
|
| Comments |
| Comment by Dmitry Agranat [ 11/Feb/21 ] | |||||
|
This error message leads us to suspect some form of physical corruption:
The ideal resolution is to perform a clean resync from an unaffected node. You can also try mongod --repair using the latest version of MongoDB. Thanks, |