[SERVER-25285] file:WiredTiger.wt read checksum error, mongodb won't start Created: 26/Jul/16  Updated: 14/Aug/18  Resolved: 29/Jul/16

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

Type: Bug Priority: Major - P3
Reporter: Joern Merkel Assignee: Kelsey Schubert
Resolution: Done Votes: 0
Labels: envns, rdi, rps, trcf, wtc
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File WiredTiger.turtle     File WiredTiger.wt     File repair-attempt.tar    
Issue Links:
Related
Operating System: ALL
Participants:

 Description   

Hi all,
I have to repair a mongodb-Setup. After a raid issue the server crashed. I tried to --repair but I got

2016-07-26T09:04:23.280+0200 E STORAGE  [initandlisten] WiredTiger (0) [1469516663:280195][5673:0x7faad17ebc80], file:WiredTiger.wt, WT_CURSOR.search_near: read checksum error for 16384B block at offset 45056: calculated block checksum of 562858221 doesn't match expected checksum of 3119024118
 
2016-07-26T09:04:23.280+0200 E STORAGE  [initandlisten] WiredTiger (0) [1469516663:280299][5673:0x7faad17ebc80], file:WiredTiger.wt, WT_CURSOR.search_near: WiredTiger.wt: encountered an illegal file format or internal value
 
2016-07-26T09:04:23.280+0200 E STORAGE  [initandlisten] WiredTiger (-31804) [1469516663:280318][5673:0x7faad17ebc80], file:WiredTiger.wt, WT_CURSOR.search_near: the process must exit and restart: WT_PANIC: WiredTiger library panic

So I tried to recover using the wt-Tools, (described here: http://www.alexbevi.com/blog/2016/02/10/recovering-a-wiredtiger-collection-from-a-corrupt-mongodb-installation/) but still, I got the same error. Every command used wit wt tools gives me the same.
So now, I have no idea how to repair that file. Since everyone sends you files, I put the WiredTiger.wt into the Attachment box.

Helps and hints are very much appreciated,
regards,
jm



 Comments   
Comment by Kelsey Schubert [ 04/Jul/17 ]

Hi ccornel,

Thanks for reporting this issue, so we can best address the issue that you've encountered. Would you please open a new ticket and attach the files there? Please be sure to include the version of MongoDB, the log message describing the failure, and a description of the events (e.g. power failure) preceding the corruption?

Thanks again,
Thomas

Comment by Carlos Cornel [ 03/Jul/17 ]

Hi

Watching this forum, I have reviewed that I have the same problem described here. And I could not give you a solution, I wanted to ask if you could see my files and be able to repair the error.

Thank you , regards.
Carlos https://drive.google.com/drive/folders/0BwyEAdclOsc_X0Nfa3RRd3RMT0k

Comment by Kelsey Schubert [ 29/Jul/16 ]

Hi jm@mpex.de,

I'm glad you were able to salvage the other collection files. WiredTiger.wt contains essential metadata for interpreting other .wt files. Unfortunately, the current process to repair these files is not ready for public consumption.

SERVER-19815 tracks improvements make make repair more robust with WiredTiger files. Please feel free to vote for it and watch it for updates.

Kind regards,
Thomas

Comment by Joern Merkel [ 28/Jul/16 ]

Hi Thomas,

thanks for repairing. Now I was able to salavage the other collection-files.
Now, could you comment what you did on this file or what metadata was in it?

best regards,
JM

Comment by Kelsey Schubert [ 27/Jul/16 ]

Hi jm@mpex.de,

I've attached the repair-attempt.tar containing the WiredTiger.wt and WiredTiger.turtle after a repair attempt. Please extract them in your dbpath and try starting mongod.

Kind regards,
Thomas

Comment by Joern Merkel [ 26/Jul/16 ]

Hi Ramon,

of course, I attached it as well. well, the process did nothing as the error was the same as with mongodb --repair. After that it was the same.
Thanks for your quck response.
Regards,
JM

Comment by Ramon Fernandez Marina [ 26/Jul/16 ]

jm@mpex.de, for us to attempt a repair we'll also need the WiredTiger.turtle file, can you please upload it as well?

Please note there are no guarantees here, as I can't vouch for the process described in the link you sent.

Thanks,
Ramón.

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