[SERVER-30635] WiredTiger read checksum error Created: 14/Aug/17 Updated: 06/Sep/17 Resolved: 15/Aug/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Bing Zou | Assignee: | Mark Agarunov |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | ALL |
| Participants: |
| Description |
|
mongo crashed again. Please help me fix mongo files. Thanks a lot. |
| Comments |
| Comment by Bing Zou [ 16/Aug/17 ] |
|
there is no backup as it's my local. I guess I will have to start from scratch. Thanks for the help. |
| Comment by Mark Agarunov [ 15/Aug/17 ] |
|
Hello xigua, Unfortunately, this error indicates that there was additional 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 Bing Zou [ 15/Aug/17 ] |
|
somehow doesn't help this time. got the following error while starting up 2017-08-15T03:56:37.725+0000 I CONTROL [initandlisten] MongoDB starting : pid=1 port=27017 dbpath=/data/db 64-bit host=2690fba6587a } ***aborting after fassert() failure This is my local mongo inside docker, the /data/db volume is mapped to local disk. My mac crashed a few time the day before which seemed cause the docker mongo failure. It's not production but I do have many databases on my local for my day to day work. My mac is late 2013 MBP with SSD and OS is Sierra. |
| Comment by Mark Agarunov [ 14/Aug/17 ] |
|
Hello xigua, 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, |