[SERVER-28866] WiredTiger.wt read checksum error Created: 19/Apr/17 Updated: 14/Aug/18 Resolved: 20/Apr/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | 3.2.12 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Adam Petschke | Assignee: | Mark Agarunov |
| Resolution: | Done | Votes: | 0 |
| Labels: | envns, rns, rps, trcf, wtc | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | ALL |
| Participants: |
| Description |
|
I am attempting to repair a corrupted db, but --repair doesn't work. I have also tried salvage with the wt tool. These are the errors: [1492617550:380374][16669:0x7f734860e700], file:WiredTiger.wt, WT_CURSOR.search_near: read checksum error for 24576B block at offset 86016: block header checksum of 2175661310 doesn't match expected checksum of 1235721632 [1492617550:380401][16669:0x7f734860e700], file:WiredTiger.wt, WT_CURSOR.search_near: WiredTiger.wt: encountered an illegal file format or internal value [1492617550:380406][16669:0x7f734860e700], file:WiredTiger.wt, WT_CURSOR.search_near: the process must exit and restart: WT_PANIC: WiredTiger library panic [1492617550:380412][16669:0x7f734860e700], txn-recover: Recovery failed: WT_PANIC: WiredTiger library panic lt-wt: WT_PANIC: WiredTiger library panic I have attached WiredTiger.wt and WiredTiger.turtle. Any help would be appreciated. Thanks, |
| Comments |
| Comment by Adam Petschke [ 19/Apr/17 ] |
|
Hi Mark, Yes, this did resolve the issue we were having. Thank you very much for the quick reply. -Adam |
| Comment by Mark Agarunov [ 19/Apr/17 ] |
|
Hello apetschke, 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, |