[SERVER-32512] WiredTiger.wt read checksum error Created: 02/Jan/18  Updated: 27/Jul/18  Resolved: 02/Jan/18

Status: Closed
Project: Core Server
Component/s: WiredTiger
Affects Version/s: 3.6.1
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Jeffrey Sica Assignee: Kelsey Schubert
Resolution: Done Votes: 0
Labels: envns, rpo, rpu, szs, trcf, wtc
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Screen Shot 2018-01-02 at 10.58.18 AM.png     File WiredTiger.turtle     File WiredTiger.wt     Text File mongod.log     File repair_attempt.tar.gz     File sizeStorer.wt    
Operating System: Linux
Participants:

 Description   

A chassis experienced a power failure with our Mongo instances on it. Attempting to run the --repair flag doesn't work and it appears the WiredTiger.wt file is corrupted.

Attached is a screenshot of the error and the relevant WiredTiger files.

Thanks!

-Jeff



 Comments   
Comment by Kelsey Schubert [ 02/Jan/18 ]

Hi jeefy,

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:

Kind regards,
Kelsey

Comment by Jeffrey Sica [ 02/Jan/18 ]

That was fast, thanks!

We've got progress but not resolution. It's now squawking about sizeStorer.wt

I've attached "sizeStorer.wt" and the startup log when running "mongod --repair"

Comment by Kelsey Schubert [ 02/Jan/18 ]

Hi jeefy,

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 so that we can further investigate.

Kind regards,
Kelsey

Generated at Thu Feb 08 04:30:27 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.