[SERVER-38525] Corrupt WiredTiger.wt mongod --repair fails to recover Created: 11/Dec/18  Updated: 20/Dec/18  Resolved: 12/Dec/18

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

Type: Bug Priority: Major - P3
Reporter: ryan Assignee: Danny Hatcher (Inactive)
Resolution: Done Votes: 0
Labels: wt-repair-success
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

I've tried with mongod --repair but no success

2018-12-10T17:18:51.303-0800 E STORAGE  [initandlisten] Failed to open a WiredTiger cursor: table:collection-2-5677681698034576038
2018-12-10T17:18:51.304-0800 E STORAGE  [initandlisten] This may be due to data corruption. Please read the documentation for starting MongoDB with --repair here: http://dochub.mongodb.org/core/repair
2018-12-10T17:18:51.304-0800 F -        [initandlisten] Fatal Assertion 50882 at src\mongo\db\storage\wiredtiger\wiredtiger_session_cache.cpp 137
2018-12-10T17:18:51.304-0800 F -        [initandlisten]***aborting after fassert() failure

I don't have any other backup available, please help.

I've attached WiredTiger files, mongod.log

 



 Comments   
Comment by Danny Hatcher (Inactive) [ 12/Dec/18 ]

Hello,

If your database is stable post-repair, you should be able to continue using it. However, please note that we strongly recommend implementing a replica set if this data is important to you so you do not run into this situation again.

Thank you,

Danny

Comment by ryan [ 12/Dec/18 ]

Yes. I'm using the same db would it cause any problems?

Comment by Danny Hatcher (Inactive) [ 11/Dec/18 ]

Hello Ryan,

So to confirm, you are now in a stable state?

Danny

Comment by ryan [ 11/Dec/18 ]

Hi Daniel,

When I ran --repair first time, it logged those errors but I tried it again now and it successfully recovered.

Thanks

 

Comment by Danny Hatcher (Inactive) [ 11/Dec/18 ]

Hello Ryan,

Would you be able to attach the output of the --repair attempt to this ticket?

Thank you,

Danny

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