[SERVER-44573] WiredTiger.wt, connection: read checksum error Created: 12/Nov/19  Updated: 18/Nov/19  Resolved: 15/Nov/19

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

Type: Bug Priority: Major - P3
Reporter: Adrian Enache Assignee: Carl Champain (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File WiredTiger.tar.gz     File mongod.log-20191109.gz     File repair_attempt.tar.gz    
Operating System: ALL
Participants:

 Description   

Hello,
After an unexpected shutdown we got this error:

2019-11-12T01:52:20.134-0500 E STORAGE [initandlisten] WiredTiger (0) [1573541540:134115][13835:0x7f3e69671c80], file:WiredTiger.wt, connection: read checksum error for 4096B block at offset 12288: block header checksum of 1043026774 doesn't match expected checksum of 1182754036
2019-11-12T01:52:20.134-0500 E STORAGE [initandlisten] WiredTiger (0) [1573541540:134212][13835:0x7f3e69671c80], file:WiredTiger.wt, connection: WiredTiger.wt: encountered an illegal file format or internal value

Could you please help us ?



 Comments   
Comment by Adrian Enache [ 18/Nov/19 ]

I will try and fix it. Thank you !

Comment by Carl Champain (Inactive) [ 15/Nov/19 ]

Hi adrian.enache@comodo.net,

The error message in the logs leads us to suspect some form of physical corruption. Please make a complete copy of the database's $dbpath directory to safeguard so that you can work off of the current $dbpath.
I've attached a repair attempt, repair_attempt.tar.gz, of the WiredTiger files you provided. Please extract these files and replace them in your $dbpath. Sadly, if this doesn't work, there is nothing else we can do to help you recover the data.

Importantly, 3.2 is already end-of-lifed, which means it is unsupported by us. We strongly recommend you upgrade to a supported version and use a replica set.

Thank you,
Carl

Comment by Adrian Enache [ 14/Nov/19 ]

Hello,

Thank you for the reply!

I've attached the log here.

Comment by Carl Champain (Inactive) [ 13/Nov/19 ]

Hi adrian.enache@comodo.net,

Thanks for the report.
To help us understand what is happening, can you please provide the full mongod.log file for this node?

Kind regards,
Carl

Generated at Thu Feb 08 05:06:21 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.