[SERVER-37309] WiredTiger.wt, connection: read checksum error for 4096B block at offset 53248: block header checksum doesn't match expected checksum Created: 25/Sep/18 Updated: 25/Oct/18 Resolved: 25/Oct/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | 3.4.11 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Yuvaraj | Assignee: | Kelsey Schubert |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | nrp, wtc | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | ALL |
| Participants: |
| Description |
|
Hi, I'm using MongoDB 3.4. We are unable to start with the backup files of /data/db. As per the documentation, tried to repair DB with the following command but same error persists.
I have attached the log file.
|
| Comments |
| Comment by Kelsey Schubert [ 25/Oct/18 ] | ||||||||||||||||||||||||
|
Hi yuvaraj We haven’t heard back from you for some time, so I’m going to mark this ticket as resolved. If this is still an issue for you, please provide additional information and we will reopen the ticket. Regards, | ||||||||||||||||||||||||
| Comment by Nick Brewer [ 26/Sep/18 ] | ||||||||||||||||||||||||
|
yuvaraj We'd like to take a closer look at what might be causing the repair to fail. Would it be possible for you to archive (tar or zip) and upload your entire dbpath directory? You can upload this information our secure portal - information shared there is only available to MongoDB employees, and is automatically removed after a period of time. Thanks, | ||||||||||||||||||||||||
| Comment by Nick Brewer [ 26/Sep/18 ] | ||||||||||||||||||||||||
|
yuvaraj Did you try booting from the same dbpath with your 3.4 installation after running the nightly build with --repair? Thanks, | ||||||||||||||||||||||||
| Comment by Yuvaraj [ 26/Sep/18 ] | ||||||||||||||||||||||||
|
Tried as per your comment. Here's the log :
| ||||||||||||||||||||||||
| Comment by Nick Brewer [ 25/Sep/18 ] | ||||||||||||||||||||||||
|
yuvaraj Thanks for the additional details. I'm actually going to suggest a different repair process for you, which involves making use of some recently introduced updates to the {{ mongod --repair}} option. Important: Before you start this process, take a backup of your dbpath via a manual copy of the directory, or a filesystem snapshot.
-Nick | ||||||||||||||||||||||||
| Comment by Yuvaraj [ 25/Sep/18 ] | ||||||||||||||||||||||||
|
Hey Nick, I have attached 2 files. The cause of the corruption (disk / filesystem failure, unexpected shutdown, etc) - It is raw data took from Folder level Backup. The platform (virtual machine, container, native hardware) - Virtual Machine | ||||||||||||||||||||||||
| Comment by Nick Brewer [ 25/Sep/18 ] | ||||||||||||||||||||||||
|
yuvaraj Thanks for your report. If you upload the WiredTiger.turtle and WiredTiger.wt files from your dbpath, we can attempt to repair them for you. We'll need to confirm:
Thanks, |