[DOCS-7793] mongodump 2.6 repair requires dbpath Created: 03/May/16  Updated: 11/Jan/17  Resolved: 04/May/16

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

Type: Improvement Priority: Minor - P4
Reporter: Andrew Ryder (Inactive) Assignee: Allison Reinheimer Moore
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Participants:
Days since reply: 7 years, 41 weeks ago

 Description   

RE: https://docs.mongodb.org/v2.6/reference/program/mongodump/#cmdoption--repair

The 2.6 variant of mongodump can only use the repair option on datafiles directly by specifying the dbpath option as well. This was traditionally the way it was, but the opposite is true in the brave new world of 3.2:
https://docs.mongodb.org/manual/reference/program/mongodump/#cmdoption--repair

The requirement should probably have always been documented, but it's gained importance now due to the change in behavior.



 Comments   
Comment by Githook User [ 04/May/16 ]

Author:

{u'username': u'schmalliso', u'name': u'Allison Moore', u'email': u'allison.moore@10gen.com'}

Message: DOCS-7793: clarify mongodump repair behavior in 2.6
Branch: v2.6
https://github.com/mongodb/docs/commit/b588cdf25161077b5aedd5b4970c466445707359

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