[SERVER-31361] Corrupt WiredTiger metadata Created: 03/Oct/17 Updated: 27/Jul/18 Resolved: 04/Oct/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | 3.2.15 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kyle Kavanagh | Assignee: | Mark Agarunov |
| Resolution: | Done | Votes: | 0 |
| Labels: | envns, rpo, rps, trcf, wtc | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | Linux |
| Participants: |
| Description |
|
Using mongodb-3.2.15 on RH7 Failing to recover from an unexpected shutdown. Attempting to startup with --repair gives the following. Attaching the metadata files - Let me know if you need any additional files
|
| Comments |
| Comment by Mark Agarunov [ 04/Oct/17 ] | ||||||||||||||||||||||||||||||||
|
Hello kdkavanagh, 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 Kyle Kavanagh [ 04/Oct/17 ] | ||||||||||||||||||||||||||||||||
|
Mark, happy to report that --repair seems to have made things whole again. Thanks for the quick help! | ||||||||||||||||||||||||||||||||
| Comment by Mark Agarunov [ 03/Oct/17 ] | ||||||||||||||||||||||||||||||||
|
Hello kdkavanagh, Thank you for the additional information. Unfortunately if running the repair is unsuccessful, it is likely due to corruption on the disk. If that is the case, my best recommendation would be to resync the affected node or restore from a backup if possible. Please let me know if the --repair has fixed this issue for you. Thanks, | ||||||||||||||||||||||||||||||||
| Comment by Kyle Kavanagh [ 03/Oct/17 ] | ||||||||||||||||||||||||||||||||
|
Thanks for the quick help Mark, The new files seem to have moved things along. Now getting the following error. Running with --repair now, will see if that fixes the issue, seems to be chugging along. If not, would I be able to email you that collection.wt file? Without knowing the contents, I'm not sure that I can post it publicly.
| ||||||||||||||||||||||||||||||||
| Comment by Mark Agarunov [ 03/Oct/17 ] | ||||||||||||||||||||||||||||||||
|
Hello kdkavanagh, 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, |