[SERVER-38634] WiredTiger.wt: encountered an illegal file format or internal value Created: 14/Dec/18 Updated: 19/Dec/18 Resolved: 19/Dec/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | 3.6.5 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Marco | Assignee: | Danny Hatcher (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | ALL |
| Participants: |
| Description |
|
Hi, after a sudden shutdown of the VM, I am encountering errors to start Mongodb. The log is attached (mongodb_log) It seems that WiredTiger files are corrupted. I tried to do a mongod --repair but I have a similar error. The log is attached (mongodb_repair_log) |
| Comments |
| Comment by Marco [ 19/Dec/18 ] | |
|
Thanks for your support. Marco | |
| Comment by Danny Hatcher (Inactive) [ 18/Dec/18 ] | |
|
Hello Marco, Unfortunately, that error indicates that the data files are unrecoverable. There is nothing else that we can do. Danny | |
| Comment by Marco [ 18/Dec/18 ] | |
|
Thank you Daniel, I tried with your files, but now I have another error. You can read the log: mongodb_startup_error_2 | |
| Comment by Danny Hatcher (Inactive) [ 17/Dec/18 ] | |
|
Hello Marco, I've attempted a manual repair of the data files. Please extract the files in repair_attempt.tar Please note that we strongly recommend replica sets for any data that is important to you in order to avoid these scenarios. Thank you, Danny | |
| Comment by Marco [ 15/Dec/18 ] | |
|
Unfortunately I don't have a replica set node. There is no way to repair the WiredTiger files? Thank you in advance | |
| Comment by Danny Hatcher (Inactive) [ 14/Dec/18 ] | |
|
Hello Marco, To resolve this issue, I would recommend a clean resync from a replica set node that is not affected. Would you be able to do so? Thank you, Danny | |
| Comment by Marco [ 14/Dec/18 ] | |
|
I'm using the following docker approach to try repair:
I tried with versions 4.0.4 and 4.1.6 of MongoDB. You can find both logs attached: | |
| Comment by Danny Hatcher (Inactive) [ 14/Dec/18 ] | |
|
Hello Marco, Could you please try running a mongod --repair with a 4.0 mongod binary? We made several large improvements to the --repair functionality in that version and I'd like to see the output of that run before proceeding. Thank you, Danny |