[SERVER-35857] Mongo db not able to start Created: 28/Jun/18  Updated: 04/Sep/18  Resolved: 29/Jun/18

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

Type: Bug Priority: Major - P3
Reporter: Syed Rahman Bokhari Assignee: Nick Brewer
Resolution: Done Votes: 0
Labels: envh, rns, rpu, trcf, wtc
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows 10


Attachments: File WiredTiger.turtle     File WiredTiger.wt     File log.2018-06-28T09-09-03     File log.2018-06-29T17-22-47     File repair-attempt.tar.gz    
Operating System: Windows
Participants:

 Description   

Unable to start mongodb server. It is contain valid data so can't afford to lose it. I can provide mdmp file.



 Comments   
Comment by Syed Rahman Bokhari [ 29/Jun/18 ]

For Journel files, in few minutes it add multiple 100 MB journel files. 

Comment by Nick Brewer [ 29/Jun/18 ]

Hi rbokhari

I'm afraid there's nothing we can do on our end to recover the data files if the repair attempt failed.

One other thing I'd note: Files in the dbPath should not be interacted with externally while they are in use by mongod - in some instances, I've seen antivirus scans on such files cause corruption.

Also, I like to ask that journel size is keep growing at alot, and reaches few GBs now.

The amount of space taken up by journal files is largely determined by the number of operations being performed. However, WiredTiger automatically removes log files - are you finding that this is not the case? How quickly is the amount of used space growing?

Nick

Comment by Syed Rahman Bokhari [ 29/Jun/18 ]

This is normal windows 10 computer with local hard drive and no replica or nodes. 

Is there any other solution that I check as per my description. Also, I like to ask that journel size is keep growing at alot, and reaches few GBs now. How to reduce that with wiredTiger storage engine.

Thanks

Comment by Nick Brewer [ 29/Jun/18 ]

rbokhari

Unfortunately, this error indicates that there was corruption on the disk, most often caused by a faulty storage layer. In this situation, our best recommendation would be to resync the affected node if it is a member of a replica set, or restore from a backup if possible.

To prevent this type of problem in the future please take note of the following guidelines to help mitigate any issues related to unreliable storage layers or server failures.

Regards,
Nick

Comment by Syed Rahman Bokhari [ 29/Jun/18 ]

Still after replacing two repaired files, mongo db service is not running. I am attaching new dump file.

Many Thanks for your timely response, can you advise further ?

 

Comment by Nick Brewer [ 29/Jun/18 ]

rbokhari

I've attached the files after a repair attempt. Would you please extract these files, substitute them for the current ones in your $dbpath, and let us know if it resolves the issue?

Thanks,
Nick

repair-attempt.tar.gz

Comment by Syed Rahman Bokhari [ 29/Jun/18 ]

I have added required two files, please have a look into it and repair those.

 

Many Thanks

Comment by Ramon Fernandez Marina [ 28/Jun/18 ]

Can you please upload the WiredTiger.wt and WiredTiger.turtle files so we can run a repair attempt?

Thanks,
Ramón.

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