[SERVER-33487] mongodb database cannot start after crash, cannot solve by --repair Created: 26/Feb/18  Updated: 21/Mar/18  Resolved: 26/Feb/18

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

Type: Bug Priority: Major - P3
Reporter: Guo Xiaohan [X] Assignee: Kelsey Schubert
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File picture1.png     PNG File picture2.png    
Operating System: ALL
Participants:

 Description   

After an unexpected crash, the database could not restart (as shown in picture 1).
I used the --repair command option, but failed at some of the point (as shown in picture 2).
If the errors came from some corrupted files, I wonder if there's some way to ignore them since the loss of some of the data is acceptable.

I'm really a freshman to this, please help me. Thanks for all of your efforts!



 Comments   
Comment by Kelsey Schubert [ 27/Feb/18 ]

Hi Jeremy Guo,

Unfortunately, given the nature of this error there may be corruption on multiple files, and, unfortunately, deleting a single file will be unlikely to resolve this issue. Additionally, please note that removing a file would cause a mismatch with the WiredTiger metadata files and prevent mongod from starting. My best recommendation would be to restore from a back up if possible.

Kind regards,
Kelsey

Comment by Guo Xiaohan [X] [ 27/Feb/18 ]

Hello Mrs.Kelsey,

Is there any possibility to delete the corrupted "log.log20180218" to restart the database successfully? Which directory should I go to? Since the boss wants to start the database as soon as possible, without caring about one day or two days' data.

Best,
Guo Xiaohan

Comment by Guo Xiaohan [X] [ 27/Feb/18 ]

Thanks a lot for your comments! I'll try it!
Next time I'll post it on other discussion groups appropriately!

Comment by Kelsey Schubert [ 26/Feb/18 ]

Hi Jeremy Guo,

An Input/output error indicates something has gone wrong on the storage layer underneath MongoDB. At this point there is no way to know the extent of the issue or whether any data recovery is possible. As next steps, I would strongly recommend checking the validity of this storage layer and attempting to move the data files to a new hardware.

Please note that the SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag. A question like this involving more discussion would be best posted on the mongodb-users group.

Kind regards,
Kelsey

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