[SERVER-34940] WiredTiger file corrupted after server crash Created: 10/May/18 Updated: 23/Jul/18 Resolved: 21/Jun/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | 3.6.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | aaerer | Assignee: | Kelsey Schubert |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
After an ungraceful shutdown, mondodb server don't start with error messages: 2018-05-11T04:41:41.191+0900 F - [initandlisten] Fatal Assertion 34433 at src/mongo/db/storage/wiredtiger/wiredtiger_record_store.cpp 633 ***aborting after fassert() failure 04:41:41 debian mongod[173015]: Version: Unable to find metadata for table:twi/collection-927-3157113709325238162 |
| Comments |
| Comment by Kelsey Schubert [ 21/Jun/18 ] |
|
Hi aaerer, 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 Kelsey Schubert [ 14/May/18 ] |
|
Hi aaerer, MongoDB 4.0 contains some improvements in this space. When it restarts from an unclean shutdown, it may automatically attempt to resolve this issue. Would you please take a back-up of your current files and then attempt to restart with the development version MongoDB 3.7.9, and let us know if it resolves the issue? If the mongod successfully starts up, I would suggest downgrading back to MongoDB 3.6 since MongoDB 3.7 isn't intended for production use and the inconsistency should now be resolved. Kind regards, |
| Comment by aaerer [ 10/May/18 ] |
|
I got this error after repairing with mongod --repair |