[SERVER-28790] Mongo does not start with current dataset Created: 13/Apr/17 Updated: 13/Aug/18 Resolved: 02/May/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code, WiredTiger |
| Affects Version/s: | 3.4.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kal | Assignee: | Kelsey Schubert |
| Resolution: | Done | Votes: | 0 |
| Labels: | envns, rfi, trcf, wtc | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Windows Server 2012 R2 |
||
| Attachments: |
|
| Operating System: | Windows |
| Participants: |
| Description |
|
Having used Mongo many times before I am having issues starting up Mongo with a particular dataset. I have included all wiredtiger files and the mongo log and would really appreciate if you could investigate this isssue asap. |
| Comments |
| Comment by Kelsey Schubert [ 02/May/17 ] |
|
Hi kal0007, From your responses, I do not see anything to indicate a bug in the MongoDB server. For MongoDB-related support, please see our Technical Support page. Thank you, |
| Comment by Kal [ 19/Apr/17 ] |
|
1. The disks are SSD's, we are not using RAID I can supply you the database files if required as we have a very high profile customer waiting for this fix. |
| Comment by Mark Agarunov [ 14/Apr/17 ] |
|
Hello kal0007, I have a few additional questions about data storage and the configuration of your environment to help us understand what's going on here. However, beware in these sorts of situations it can be difficult to understand the cause of the corruption without a straightforward reproduction.
Thanks, |
| Comment by Mark Agarunov [ 14/Apr/17 ] |
|
Hello kal0007, Thank you for the report. Unfortunately the error in the logs indicates that there was likely corruption in the underlying storage layer. I would recommend a clean resync from a node that is not affected or restoring from a backup. Thanks, |