[SERVER-46728] Corrupted db - WiredTiger error Created: 09/Mar/20  Updated: 11/Mar/20  Resolved: 11/Mar/20

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

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

Attachments: File WiredTiger.turtle     File WiredTiger.wt     File repair_attempt.tar.gz    
Operating System: ALL
Participants:

 Description   

Hi All,

based on my research and previous Jira case I'd conclude my db is corrupted. I have tried to --repair it, but without luck.

 

Error message I got when starting repair:

2020-03-09T20:01:27.086+0100 E STORAGE [initandlisten] WiredTiger (0) [1583780487:86704][9188:0x7f07a83f1540], file:WiredTiger.wt, connection: read checksum error for 4096B block at offset 12288: block header checksum of 4237130932 doesn't match expected checksum of 3128355512
2020-03-09T20:01:27.086+0100 E STORAGE [initandlisten] WiredTiger (0) [1583780487:86790][9188:0x7f07a83f1540], file:WiredTiger.wt, connection: WiredTiger.wt: encountered an illegal file format or internal value
2020-03-09T20:01:27.086+0100 E STORAGE [initandlisten] WiredTiger (-31804) [1583780487:86807][9188:0x7f07a83f1540], file:WiredTiger.wt, connection: the process must exit and restart: WT_PANIC: WiredTiger library panic

Please find WiredTiger.wt and WiredTiger.turtle in attachement.

Is there any chance to recover my corrupted db?

Thnak you.

 

Y



 Comments   
Comment by Carl Champain (Inactive) [ 11/Mar/20 ]

Glad to hear that the repair worked! I'm now closing this ticket.

Comment by B C [ 11/Mar/20 ]

Hi Carl,

you're amazing, I had to tune a bit some permission, but restore itself works like charm. Thank you.

5 of 5.

Y

Comment by Carl Champain (Inactive) [ 10/Mar/20 ]

Hi micha.z4nd4r@gmaiil.com,

I've attached a repair attempt of the files you provided as repair_attempt.tar.gz. Please extract these files, replace them in your $dbpath, and let us know if it resolves the issue—keep in mind that this repair effort may not be successful.

Kind regards,
Carl

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