[SERVER-32676] WiredTiger.wt file corrupted after unclean shutdown, cannot start Created: 12/Jan/18 Updated: 22/Feb/18 Resolved: 22/Jan/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Guilherme Siqueira Marques da Silva | Assignee: | Mark Agarunov |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | ALL |
| Participants: |
| Description |
|
We run MongoDB 3.2.11 in an OpenShift cluster and the pod had stopped stopped improperly, corrupting the WiredTiger data files. The error is basically the same as described in file:WiredTiger.wt, connection: unable to read root page from file:WiredTiger.wt: WT_ERROR: non-specific WiredTiger error Could you please repair the files? Thany you |
| Comments |
| Comment by Mark Agarunov [ 22/Jan/18 ] |
|
Hello guilherme.smdsd, We haven’t heard back from you for some time, so I’m going to mark this ticket as resolved. If this is still an issue for you, please provide additional information and we will reopen the ticket. Thanks, |
| Comment by Mark Agarunov [ 12/Jan/18 ] |
|
Hello guilherme.smdsd, Thank you for your report. I've attached a repair attempt of the files you provided. Please extract these files and replace them in your $dbpath and let us know if it resolves the issue. If you are still seeing errors after replacing these files, please provide the complete logs from the affected node(s) so that we can further investigate. Thanks, |