[SERVER-33414] Corrupted database can't salvage checksum issue Created: 21/Feb/18  Updated: 21/Mar/18  Resolved: 21/Feb/18

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

Type: Bug Priority: Major - P3
Reporter: Pablo Velasquez Assignee: Kelsey Schubert
Resolution: Done Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: HTML File WiredTiger     File WiredTiger.basecfg     File WiredTiger.turtle     File WiredTiger.wt     File repair_attempt.tar.gz     File sizeStorer.wt     File storage.bson    
Operating System: ALL
Participants:

 Description   

As per the other tickets about this issue we are unable to salvage

I am attaching the files so that you can help me with the repair as in the other tickets

Thank You

Mongo version: 3.08

file:WiredTiger.wt, connection: read checksum error for 4096B block at offset 12288: block header checksum of 3397587970 doesn't match expected checksum of 978874730
[1519180958:967760][9535:0x7f4a854b5700], file:WiredTiger.wt, connection: WiredTiger.wt: encountered an illegal file format or internal value
[1519180958:967810][9535:0x7f4a854b5700], file:WiredTiger.wt, connection: the process must exit and restart: WT_PANIC: WiredTiger library panic
lt-wt: WT_PANIC: WiredTiger library panic



 Comments   
Comment by Pablo Velasquez [ 22/Feb/18 ]

Hi Kelsey
the files worked very good to be able to do the salvage, but we are missing 1 year of data, is it possible for the metadata files to be pointing now to older data and for the new data to still be on the .wt files?

do you guys offer a service for data recovery? or do you know of a company for this?

Comment by Kelsey Schubert [ 21/Feb/18 ]

Hi pablo.velasquez,

Thanks for your response. I'm glad to hear that this fixed the issue and everything is working again. 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 or server failures:

Thank you,
Kelsey

Comment by Pablo Velasquez [ 21/Feb/18 ]

Thank you!
Thank you!
Thank you!
it worked!

Comment by Kelsey Schubert [ 21/Feb/18 ]

Hi pablo.velasquez,

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.

Thank you,
Kelsey

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