[SERVER-38213] mongodb server can not startup,the wiredtiger file corrupted Created: 20/Nov/18 Updated: 05/Dec/18 Resolved: 05/Dec/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 3.2.11 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | sushi feng | Assignee: | Danny Hatcher (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | WiredTiger | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
operating system: windows server 2012 |
||
| Attachments: |
|
| Participants: |
| Description |
|
The power failure caused the mongodb server abnormal shutdown.Then it can not startup,the wiredtiger file corrupted. log as fellows: 1.unable to read root page from file:WiredTiger.wt:WT_ERROR :no-specific WiredTiger error 2.Wired Tiger has failed to open its meta data 3.This may be due to the database files being encrypted,being from an older or due to the corruption on disk 4: You should confirm that you have opened the database with the correct options including all encryption and compression option. |
| Comments |
| Comment by Danny Hatcher (Inactive) [ 05/Dec/18 ] |
|
Hello, I'm sorry to hear that. Unfortunately there is nothing else that we can do. To prevent this type of problem in the future please take note of the following guidelines to help mitigate any issues related to unreliable storage layers or server failures.
Thank you, Danny |
| Comment by sushi feng [ 05/Dec/18 ] |
|
Today I have tried to start the mongodb with a replacement of the file you have repaired.But unluckly it can not start ,thank you all the same. |
| Comment by Danny Hatcher (Inactive) [ 27/Nov/18 ] |
|
Hello, I have attempted a repair on the WiredTiger metadata and have uploaded it to this ticket as WiredTiger.tar Thank you, Danny |
| Comment by sushi feng [ 27/Nov/18 ] |
|
Our java web application has just online for several months and We haven't had time to make a backup yet and deployed in standalone mode. so.....Tragedy happened. And the disk is well, in fact the disk we used to istall mongodb is the Storage array.Is it really impossible to repair the meta data *.wt file ?we are very anxious。 |
| Comment by Danny Hatcher (Inactive) [ 26/Nov/18 ] |
|
Hello Rafael, Unfortunately, this error indicates that there was corruption on the disk, most likely caused by the power failure. In this situation, our best recommendation would be to resync the affected node or restore from a backup if possible. Do you have either option available to you? Thank you, Danny |