[SERVER-25367] WT_ERROR: non-specific WiredTiger error, terminating Created: 01/Aug/16 Updated: 02/Feb/22 Resolved: 04/Oct/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | 3.2.6 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Tsedendamba | Assignee: | Kelsey Schubert |
| Resolution: | Done | Votes: | 0 |
| Labels: | envns, rpo, trcf, wtc | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Operating System: | Windows | ||||||||
| Participants: | |||||||||
| Description |
|
| Comments |
| Comment by Kelsey Schubert [ 04/Oct/16 ] |
|
Hi tsedendamba, Sorry for the silence, we've been discussing whether there is anything more that we can do in this situation. Unfortunately, it appears that the power failure lead to file system corruption, which affected the MongoDB data files. In this situation, there is little that MongoDB can do other than report that the files have become corrupted. Kind regards, |
| Comment by Tsedendamba [ 02/Aug/16 ] |
|
I using windows 10. Unplanned power outage and unclean shutdown. After mongodb not started. My storage device is SATA. I don't now how to check file health. How to check file? My db path is c:/data/db default path. mongod --repair command after that log C:\Users\1>mongod -repair 2016-08-02T09:28:05.738+0900 I - [initandlisten] Detected data files in C:\data\db\ created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'. |
| Comment by Ramon Fernandez Marina [ 01/Aug/16 ] |
|
Sorry you've run into this issues tsedendamba. You're getting this message because the WiredTiger.wt file got corrupted. Can you please provide more details on the events leading up to this problem? For example, did you have any unclean shutdowns? Note also the file corruption may be caused by an unhealthy storage layer. What type of storage devices are you using? Have you check their health recently? If you can upload full logs for this node as well as a full directory listing of the contents of your dbpath that may also help with the investigation. Thanks, |