[SERVER-36293] file:WiredTiger.wt, connection: WiredTiger.turtle: encountered an illegal file format or internal value (after server crash) Created: 26/Jul/18 Updated: 30/Jul/18 Resolved: 26/Jul/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | 3.6.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Birmjin In | Assignee: | Nick Brewer |
| Resolution: | Done | Votes: | 0 |
| Labels: | envns, rns, trct, wtc | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | Linux |
| Participants: |
| Description |
|
Hello, I'm using v3.6.4. I'm unable to restart Mongod process after server crash. I tried --repair option as manual indicates, but had no progress. I've uploaded my WiredTiger.* files plus mongod.log file in the hope that someone can respond with fixed WiredTiger.* files. I would be extremely grateful...thank you!
|
| Comments |
| Comment by Nick Brewer [ 26/Jul/18 ] |
|
birmjin It looks like the WiredTiger.turtle file you've uploaded is badly corrupted - this file contains the metadata that is used to interpret WiredTiger.wt, which is in turn used to interpret all other .wt files. With that file in its current state, any repair attempts we make are going to be unsuccessful. In this situation, our best recommendation would be to resync the affected node if it is a replica set member, or restore from a backup if one is available. Some guidelines for avoiding issues related to unreliable storage layers or server failures:
Regards, |