[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/ 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: |
| Comment by Githook User [ 24/Jan/18 ] |
|
Author: {'name': 'Andrew Aldridge', 'email': 'i80and@foxquill.com', 'username': 'i80and'}Message: |
| Comment by Githook User [ 23/Jan/18 ] |
|
Author: {'name': 'Andrew Aldridge', 'email': 'i80and@foxquill.com', 'username': 'i80and'}Message: |