[DOCS-9839] Documentation on --repair command Created: 31/Jan/17  Updated: 24/Jan/18  Resolved: 23/Jan/18

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Diana Esteves (Inactive) Assignee: Andrew Aldridge
Resolution: Done Votes: 0
Labels: mongodump
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 6 years, 3 weeks, 1 day ago
Story Points: 0.5

 Description   

https://docs.mongodb.com/manual/reference/program/mongodump/
"--repair is only available for use with mongod instances using the mmapv1 storage engine. You cannot run --repair with mongos or with mongod instances that use the wiredTiger storage engine. To repair data in a mongod instance using wiredTiger use mongod --repair."

I think we should clarify that mongod --repair is the preferred method to recover data after experiencing data corruption regardless of storage engine, and possibly link to https://docs.mongodb.com/manual/tutorial/recover-data-following-unexpected-shutdown/



 Comments   
Comment by Githook User [ 24/Jan/18 ]

Author:

{'name': 'Andrew Aldridge', 'email': 'i80and@foxquill.com', 'username': 'i80and'}

Message: DOCS-9839: Clarify that mongod --repair is preferred
Branch: v3.2
https://github.com/mongodb/docs/commit/c7e5f281e39856f1c3cff0a62f14b54e64970813

Comment by Githook User [ 24/Jan/18 ]

Author:

{'name': 'Andrew Aldridge', 'email': 'i80and@foxquill.com', 'username': 'i80and'}

Message: DOCS-9839: Clarify that mongod --repair is preferred
Branch: v3.4
https://github.com/mongodb/docs/commit/4dabff986ffc07ab39b3ce741e141ede2eac9306

Comment by Githook User [ 23/Jan/18 ]

Author:

{'name': 'Andrew Aldridge', 'email': 'i80and@foxquill.com', 'username': 'i80and'}

Message: DOCS-9839: Clarify that mongod --repair is preferred
Branch: master
https://github.com/mongodb/docs/commit/c1ec85aef3108cef1100075cc7b40c1a8b382d16

Generated at Thu Feb 08 07:59:16 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.