[SERVER-35942] WiredTiger won't recognized collections Created: 02/Jul/18 Updated: 14/Aug/18 Resolved: 02/Jul/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | 3.6.5 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Ubirata Bezerra | Assignee: | Nick Brewer |
| Resolution: | Done | Votes: | 0 |
| Labels: | envm, rge, rpu, trct, wtc | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Debian 9.0 with Graylog 2.4.5 and elasticsearch 5.6.10 |
||
| Attachments: |
|
| Operating System: | Linux |
| Participants: |
| Description |
|
Dears, A few days ago, when I ran a VM snapshot, My VM crashed with Graylog application. Other packages and configurations has still OK, but the MongoDB doesn't. When I run command to start mongoDB, I have this error:
This is result: 2018-06-28T15:22:47.718-0300 I - [initandlisten] Detected data files in /srv/data/mongodb created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'. ***aborting after fassert() failure |
| Comments |
| Comment by Nick Brewer [ 02/Jul/18 ] |
|
Hi usbezerra It looks like the WiredTiger.turtle file you've uploaded is badly corrupted - this file contains the metadata that is used to interpret WiredTiger.wt, which is in turn used to interpret all other .wt files. With that file in its current state, any repair attempts we make are going to be unsuccessful. In this situation, our best recommendation would be to resync the affected node if it is a replica set member, or restore from a backup if one is available. Some guidelines for avoiding issues related to unreliable storage layers or server failures:
Regards, |
| Comment by Ubirata Bezerra [ 02/Jul/18 ] |
|
i'd like to start recover this database, or help to reach it. If doesn't, i'd like to read theses collections or export them to another server already started. |