Operational Defect Database

BugZero found this defect 2501 days ago.

MongoDB | 375498

[SERVER-28866] WiredTiger.wt read checksum error

Last update date:


Affected products:

MongoDB Server

Affected releases:


Fixed releases:

No fixed releases provided.



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, Adam

Top User Comments

apetschke commented on Wed, 19 Apr 2017 20:48:49 +0000: Hi Mark, Yes, this did resolve the issue we were having. Thank you very much for the quick reply. -Adam mark.agarunov commented on Wed, 19 Apr 2017 17:14:51 +0000: 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: What kind of underlying storage mechanism are you using? Are the storage devices attached locally or over the network? Are the disks SSDs or HDDs? What kind of RAID and/or volume management system are you using? Would you please check the integrity of your disks? Has the database always been running this version of MongoDB? If not please describe the upgrade/downgrade cycles the database has been through. Have you manipulated (copied or moved) the underlying database files? If so, was mongod running? Have you ever restored this instance from backups? What method do you use to create backups? When was the underlying filesystem last checked and is it currently marked clean? Thanks, Mark

Additional Resources / Links


BugZero Risk Score

Coming soon



Have you been affected by this bug?


Do you know how much operational outages are costing you?

Understand the cost to your business and how BugZero can help you reduce those costs.


Login to read and write comments.

Have you ever...

had your data corrupted from a