[SERVER-60692] One of my production mongodb standalone instance is not repairing after a unexpected shutdown Created: 14/Oct/21 Updated: 20/Oct/21 Resolved: 20/Oct/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Nitin Garg | Assignee: | Edwin Zhou |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | ALL |
| Participants: |
| Description |
|
After an unxpected shutdown, my mongodb server is not starting up. I have tried using --repair but it is still not working. I am attaching the log file for reference. Any help will be highly appreciated. Thanks Nitin |
| Comments |
| Comment by Edwin Zhou [ 20/Oct/21 ] |
|
Thank you for following up. Unfortunately, without a backup of the $dbpath we will not be able to repair this corruption. To avoid a problem like this in the future, it is our strong recommendation to:
Best, |
| Comment by Nitin Garg [ 18/Oct/21 ] |
|
Hi Edwin, Unfortunately not. We didn't create a backup of dbpath before running --repair. Is there any way/recommendations to deal with this sort of issue, if it ever happen again in future? Thanks |
| Comment by Edwin Zhou [ 18/Oct/21 ] |
|
Thanks for your report. This appears to be corruption on the database which resulted from the unclean shutdown. Prior to running --repair, did you first create a backup of your database's $dbpath directory to safeguard so you can work off of your current $dbpath? Best, |
| Comment by Nitin Garg [ 14/Oct/21 ] |
|
MongoDB version: v4.4.1 |