[DOCS-8231] Clarify the steps regarding repair data files and preserve original files Created: 08/Jul/16 Updated: 30/Oct/23 Resolved: 29/Aug/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Linda Qin | Assignee: | Kay Kim (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Days since reply: | 7 years, 24 weeks, 2 days ago | ||||||||||||||||||||||||
| Story Points: | 0.25 | ||||||||||||||||||||||||
| Description |
|
This is for the following document: This document describes repairing the data files using the --repairpath option to preserve the original data files unmodified. However, from the docs for --repairpath:
There will be no data under the --repairpath directory after repair completes. So Step 2 to start mongod with the new data directory doesn't make sense. --repairpath is only to specify the tmp directory used for repair and it cannot used to preserve the original data files for repairing. User should take a backup of the data files before repairing, rather than relying on --repairpath. |
| Comments |
| Comment by Githook User [ 29/Aug/16 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |
| Comment by Githook User [ 29/Aug/16 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |
| Comment by Michael Cahill (Inactive) [ 13/Jul/16 ] |
|
In |
| Comment by Linda Qin [ 13/Jul/16 ] |
|
Also, currently only the MMAPv1 storage engine will acknowledge the --repairPath option. Please refer to |