[SERVER-42601] WiredTiger.wt: encountered an illegal file format or internal value Created: 02/Aug/19 Updated: 22/Aug/19 Resolved: 06/Aug/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | 3.4.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | tef sky | Assignee: | Danny Hatcher (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | envns, rpo, rps, trcf, wt-repair-success, wtc | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Linux |
||
| Attachments: |
|
| Operating System: | ALL |
| Participants: |
| Description |
|
Hello, so after a bad server/mongod shutdown, I am unable to restart Mongod. I'm 99% confident that my issue is that same as This one. Like the above thread, I've uploaded my WiredTiger.* files in the hopes that someone can respond with fixed WiredTiger.* files. I would be extremely grateful...thank you! If anyone has any further questions, feel free to ask. Thank you!!
https://jira.mongodb.org/browse/SERVER-26103 我的英语很差,很抱歉。因此我拷贝了一份相同问题的副本来描述问题 。 |
| Comments |
| Comment by Danny Hatcher (Inactive) [ 06/Aug/19 ] |
|
Glad to hear it! In addition to the backup, we do recommend configuring any production system to be a three-member replica set. That way, if you do have corruption on one node, you will still have two healthy nodes and you will not lose any data. |
| Comment by tef sky [ 06/Aug/19 ] |
|
Thank you very much for saving my life. The database has been repaired successfully and is in the process of backup. |
| Comment by Danny Hatcher (Inactive) [ 05/Aug/19 ] |
|
The ideal resolution is to perform a clean resync from an unaffected node. You can also try mongod --repair]. Please try one of these options before using the repaired files. If neither of the two options above work, please replace the WiredTiger.wt and WiredTiger.turtle files in your $dbpath with repair_attempt.tgz |