[SERVER-30753] Wiredtiger.wt likely corrupted Created: 20/Aug/17 Updated: 27/Jul/18 Resolved: 29/Aug/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | 3.2.16 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Anuj Gupta | Assignee: | Mark Agarunov |
| Resolution: | Done | Votes: | 0 |
| Labels: | envm, rge, rpu, szs, trcf, wtc | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | Linux |
| Participants: |
| Description |
|
Hello, My mongodb likely had an unclean shutdown and i have spent days trying to get it back up. I am able to start a new mongodb instance in a new location but cannot get my old one with all of my old collections and indexes to work properly. When I try to repair it, it gives the following message:
From past people experiencing the same issues, it would appear my WiredTiger.rt is corrupted? Can anyone please assist with these issues? I have attached my associated WiredTiger.rt files. |
| Comments |
| Comment by Mark Agarunov [ 29/Aug/17 ] | |||||||||||||||||||||||||||||||||||||||||||||||
|
Hello anujgupta201121, Unfortunately, this error indicates that there was corruption on the disk. In this situation, my best recommendation would be to resync the affected node or restore from a backup if possible. Thanks, | |||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Anuj Gupta [ 23/Aug/17 ] | |||||||||||||||||||||||||||||||||||||||||||||||
|
From my understanding, it is actually the mongodb_catalog file that is also corrupted. Is there any way you would be able to repair that? | |||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Anuj Gupta [ 21/Aug/17 ] | |||||||||||||||||||||||||||||||||||||||||||||||
|
Unfortunately it did not work. I ran it on port 27117. I attached the log file. Keep in mind i am running a new mongod instance temporarily with empty data on the default port till i am able to get the old one up. It is what you likely will see in the logs. I added the configuration file as well. The error message is also below:
In terms of your questions: 1. I am running it on an AWS EC2 instance. I believe it is is SSD. 2. I verified with AWS support, there is no issue with the integrity of the disk. 3. The database has always been running this version. 4. I did likely move the database files in trying to get the database back up. The mongod may have been running without me realizing it. 5. It has not been restored. 6. I had no backups (although i corrected that issue now) 7. It is marked clean. i had aws support check in the last 24 hours. | |||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Mark Agarunov [ 21/Aug/17 ] | |||||||||||||||||||||||||||||||||||||||||||||||
|
Hello anujgupta201121, Thank you for the report. I've attached a repair attempt of the files you've provided. Would you 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 mongod so that we can further investigate. Additionally, if this issue persists, please provide the following information:
Thanks, | |||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Anuj Gupta [ 21/Aug/17 ] | |||||||||||||||||||||||||||||||||||||||||||||||
|
Really appreciate you looking into this. I have uploaded the WiredTiger.turtle | |||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Mark Agarunov [ 21/Aug/17 ] | |||||||||||||||||||||||||||||||||||||||||||||||
|
Hello anujgupta201121, Thank you for the report. Would you please upload the WiredTiger.turtle file in addition to the WiredTiger.wt file that you've already uploaded so we can attempt a repair? Thanks, |