[SERVER-27947] Failed to repair mongo after system crash Created: 08/Feb/17 Updated: 13/Aug/18 Resolved: 21/Feb/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin |
| Affects Version/s: | 3.2.5 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Thoang Tran | 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 | ||
| Environment: |
db version v3.2.5 |
||
| Attachments: |
|
| Operating System: | Linux |
| Participants: |
| Description |
|
The system was crushed, but when i start mong with --repair key , i got read checksum error:
Pls support me resolve this problem, |
| Comments |
| Comment by Mark Agarunov [ 17/Feb/17 ] |
|
Hello vagabond_vn, I'm glad to hear that the repair worked. Unfortunately, in cases like this it is not clear what failure caused the corruption you observed. If you encounter this issue again, I would recommend checking the integrity of your storage layer. However, please be aware that MongoDB 3.2.5 is affected by Thanks, |
| Comment by Thoang Tran [ 17/Feb/17 ] |
|
Hello @Mark Agarunov, |
| Comment by Mark Agarunov [ 16/Feb/17 ] |
|
Hello vagabond_vn, I'm glad to hear that the repair was a success. I've attached a repair attempt of the newer files you've provided. Would you please extract these files and replace them in your $dbpath as before and let us know if it resolves the issue? Thanks, |
| Comment by Thoang Tran [ 16/Feb/17 ] |
|
Thanks for support, |
| Comment by Mark Agarunov [ 08/Feb/17 ] |
|
Hello vagabond_vn, 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? Thanks, |