[SERVER-31931] Corrupt database after unexpected shutdown Created: 13/Nov/17 Updated: 07/Dec/17 Resolved: 14/Nov/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 3.2.14 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | NidgetGod | Assignee: | Mark Agarunov |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | ALL |
| Participants: |
| Description |
|
MongoDB shell version: 3.2.14 Using wt
display
And mongod --repair --dbpath=/data/db --storageEngine=wiredTiger display
|
| Comments |
| Comment by Mark Agarunov [ 14/Nov/17 ] |
|
Hello nidgetgod, Thanks for your response. I'm glad to hear that this fixed the issue and everything is working again. To prevent this type of problem in the future, we recommend implementing regular backups and/or replication to mitigate any issues related to unreliable storage layers or server failures. Thanks, |
| Comment by NidgetGod [ 14/Nov/17 ] |
|
Hi Mark, It work. Thanks. And is any solution we can repair by ourselves? by N |
| Comment by Mark Agarunov [ 13/Nov/17 ] |
|
Hello nidgetgod, Thank you for the report. I've attached a repair attempt of the files you've provided. Would you 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 mongod so that we can further investigate. Additionally, if this issue persists, please provide the following information:
Thanks, |