[SERVER-30364] file:WiredTiger.wt, connection: WiredTiger.turtle: encountered an illegal file format or internal value Created: 27/Jul/17 Updated: 27/Jul/18 Resolved: 02/Aug/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 3.4.5 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Rahul Ranjan | Assignee: | Mark Agarunov |
| Resolution: | Done | Votes: | 0 |
| Labels: | envh, rge, rpu, trct, wtc | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | Linux |
| Participants: |
| Description |
|
I'm not able to restart mongodb after reboot. I'm uploading the WiredTiger.* files for your reference. I tried running mongod --repair but found the same issue. |
| Comments |
| Comment by Ramon Fernandez Marina [ 06/May/18 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Apologies for the delay Durbala. When the underlying storage layer isn't reliable enough, unfortunately there may be no way to do any further recovery of the data. Regards, | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Maxim [X] [ 19/Apr/18 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Good day Mark, thank you for quick response. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Mark Agarunov [ 02/Aug/17 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Hello rahul_ranjan, 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. Thanks, | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Rahul Ranjan [ 27/Jul/17 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
1. I'm using SSD. The storage device is locally attached. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Rahul Ranjan [ 27/Jul/17 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Hi, Thanks for replying. I replaced the files as provided by you and ran mongod --dbpath /var/lib/mongodb/ --port 27018. I got the following error:
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Mark Agarunov [ 27/Jul/17 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Hello rahul_ranjan, 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? If you are still seeing errors after replacing these files, please provide the complete logs from mongod so that we can further investigate. Additionally, if this issue persists, please provide the following information:
Thanks, |