[SERVER-22816] Corrupt metadata after unexpected shutdown -> unable to start or repair Created: 23/Feb/16 Updated: 10/Mar/16 Resolved: 10/Mar/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Alexandru Dobre | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
Using mongodb 3.0.1 with wiredTiger |
| Comments |
| Comment by Kelsey Schubert [ 10/Mar/16 ] |
|
Hi a.dobre, Unfortunately, repairDatabase cannot continue when it hits an empty collection file. There is an improvement planned, If you are able, I would recommend resyncing from an unaffected node or restoring from a backup. For MongoDB-related support discussion please post on the mongodb-users group or Stack Overflow with the mongodb tag. A question like this involving more discussion would be best posted on the mongodb-users group. Kind regards, |
| Comment by Alexandru Dobre [ 23/Feb/16 ] |
|
Hello and thank you for the file fixes. Thanks, |
| Comment by Ramon Fernandez Marina [ 23/Feb/16 ] |
|
a.dobre, can you please extract the repair_attempt.tgz files in your dbpath and start mongod again? Thanks, |
| Comment by Ramon Fernandez Marina [ 23/Feb/16 ] |
|
a.dobre, there are some known issues with early 3.0 releases where unclean shutdowns may leave some of the WiredTiger files in an unclean state and prevent startup. I'll try to repair these files and upload the results. In the meantime I strongly urge you to upgrade to the latest MongoDB version (3.0.9 in the v3.0 branch, 3.2.3 in the v3.2 branch). |