[SERVER-26998] Unhandled exception 0xC0000006 while performing recovery Created: 11/Nov/16 Updated: 15/Nov/16 Resolved: 14/Nov/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 3.2.10 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jan S. | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | ALL |
| Steps To Reproduce: | Unknown |
| Participants: |
| Description |
|
The database was shut down cleanly, however it seems like something went wrong during shutdown because when mongod is now started it start a recover - which fails with an Last stack trace entry is ...\src\mongo\db\storage\mmap_v1\dur_journal.cpp(148) mongo::dur::JSectFooter::checkHash+0x29 |
| Comments |
| Comment by Jan S. [ 15/Nov/16 ] |
|
Hi Thomas, thanks for the feedback. You are right, one of the files in the journal directory was totally unreadable. |
| Comment by Kelsey Schubert [ 14/Nov/16 ] |
|
Hi mango, Thanks for your report. The error message in the log indicates that there was an I/O failure. I would recommend examining the system logs and investigating the integrity of your storage layer. Unfortunately, in this case there isn't anything MongoDB can gracefully catch this exception. Please note that SERVER project is for reporting bugs or feature suggestions for the MongoDB server. 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, |