[SERVER-37322] Cannot repair mongodb instance without WiredTiger.turtle file Created: 26/Sep/18 Updated: 26/Sep/18 Resolved: 26/Sep/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 3.2.10 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Vyacheslav Salakhutdinov | Assignee: | Nick Brewer |
| Resolution: | Done | Votes: | 0 |
| Labels: | envm, rdi, trct, wtc | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | Linux |
| Participants: |
| Description |
|
After disk outage WiredTiger.turtle became zero-length.
Is it possible to repair db? |
| Comments |
| Comment by Vyacheslav Salakhutdinov [ 26/Sep/18 ] |
|
I restored my collection data with this guide:
Also I see that added ability to recovery metadata: https://jira.mongodb.org/browse/SERVER-35629 Maybe there is a possibility to restore the metadata manually for whole db? |
| Comment by Nick Brewer [ 26/Sep/18 ] |
|
megazoll Thanks for the platform info. Unfortunately there's not a way to extract the collection data without the underlying metadata that is used to interpret it. Sorry we can't be of more help here - let us know if you have any additional questions. -Nick |
| Comment by Vyacheslav Salakhutdinov [ 26/Sep/18 ] |
|
Debian on VM(KVM).
If there is no way to repair whole instance, Is there any chance to extract data from some collection? |
| Comment by Nick Brewer [ 26/Sep/18 ] |
|
megazoll The WiredTiger.turtle file contains metadata that is used to interpret the WiredTiger.wt file, which in turn is used to interpret all other .wt files that store collections and indexes in your dbpath. As such, I'm afraid we don't have a way to repair a database with an empty .turtle file. Your best option in this case would be to restore from any backups you have available, or to resync this node if it is a member of a replica set. So that we can better track this issue, it would be useful to confirm the platform on which the mongod is running (virtual machine, container, native hardware, etc). Thanks in advance for any details you can provide. -Nick |