[SERVER-33225] WiredTiger.wt: encountered an illegal file format or internal value Created: 09/Feb/18 Updated: 21/Mar/18 Resolved: 09/Feb/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Mohammad majidi | Assignee: | Kelsey Schubert |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | ALL |
| Participants: |
| Description |
|
I am using mongodb 3.6, storage engine - wiredTiger
So I tried to repair mongodb with this command :
This is what happend :
I know this is like a duplicate to other issues but after searching for a whole day I realized that WiredTiger.* files shoud be repaired so I've attached this files to this ticket, so maybe you could fix this files . |
| Comments |
| Comment by Kelsey Schubert [ 09/Feb/18 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Hi mr96robot Unfortunately, this error indicates that there was corruption on the disk, most often cause by a faulty storage layer. In this situation, our best recommendation would be to resync the affected node or restore from a backup if possible. 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.
Kind regards, | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Mohammad majidi [ 09/Feb/18 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Dear @Kelsey.T.Schubert Thank you for responding.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Kelsey Schubert [ 09/Feb/18 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Hello mr96robot, Thank you for your report. I've attached a repair attempt of the files you provided. Please extract these files and replace them in your $dbpath and let us know if it resolves the issue. If you are still seeing errors after replacing these files, please provide the complete logs from the affected node(s) so that we can further investigate. Thanks, | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Mohammad majidi [ 09/Feb/18 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
please please please help me | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Mohammad majidi [ 09/Feb/18 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Any advices ? |