[SERVER-29312] WiredTiger.wt: encountered an illegal file format or internal value Created: 22/May/17 Updated: 27/Jul/18 Resolved: 23/May/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | 3.4.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Sophie Perrineau | Assignee: | Mark Agarunov |
| Resolution: | Done | Votes: | 0 |
| Labels: | envns, rpo, rps, trcf, wtc | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | Linux |
| Participants: |
| Description |
|
Hello, } I join to this ticket the wirertiger.wt files, and i hope that someone can repair it |
| Comments |
| Comment by Mark Agarunov [ 23/May/17 ] |
|
Hello infrastructure, Thank you for providing the additional information. Unfortunately, this error indicates that there was corruption on the disk. In this situation, my best recommendation would be to resync the affected node or restore from a backup if possible. Please note that SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support see our Technical Support page for additional resources. Thanks, |
| Comment by Sophie Perrineau [ 23/May/17 ] |
|
Hello,
Is there a way to force the content of this collection to empty in order to repair the other files ? |
| Comment by Mark Agarunov [ 23/May/17 ] |
|
Hello infrastructure, I'm glad to hear the repaired files worked. I've attached a repair attempt of the second set of files you've provided. Would you please extract these files and replace them in your $dbpath as with the previous set and let us know if it resolves the issue? Thanks, |
| Comment by Sophie Perrineau [ 23/May/17 ] |
|
The first DB is started without errors now. But we're still waiting for a solution for the other shard which has exactly the same problem (the damaged files are in the zip named wd06.zip). |
| Comment by Sophie Perrineau [ 23/May/17 ] |
|
The first db seems to be OK (repair process ongoing). Could you please do the same operation for the second DB : the files are in the zip named wd06.zip |
| Comment by Mark Agarunov [ 22/May/17 ] |
|
Hello infrastructure, Thank you for the report. I've attached a repair attempt of the files you've provided. Would you please extract these files and replace them in your $dbpath and let us know if it resolves the issue? Thanks, |
| Comment by Sophie Perrineau [ 22/May/17 ] |
|
I have the same problem on a second server. Here are the corrupted files. |