Details
-
Bug
-
Resolution: Done
-
Major - P3
-
None
-
None
-
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:
Specifies a working directory that MongoDB will use during the --repair operation. After --repair completes, the data files in option: --dbpath and the --repairpath directory is empty.
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.
Attachments
Issue Links
- is duplicated by
-
DOCS-7203 "Recover Data after an Unexpected Shutdown" tutorial needs to be updated for WiredTiger
-
- Closed
-
-
DOCS-7302 Comment on: "manual/tutorial/recover-data-following-unexpected-shutdown.txt"
-
- Closed
-
-
DOCS-8085 Comment on: "manual/tutorial/recover-data-following-unexpected-shutdown.txt"
-
- Closed
-
- related to
-
SERVER-25008 Disallow repairPath with non-mmap storage engines
-
- Closed
-