Details
-
Bug
-
Resolution: Done
-
Minor - P4
-
None
-
3.0.11
-
None
-
Windows Server 2012 R2
Description
We ran the following command
C:\Program Files\MongoDB\Server\3.0\bin>mongodump --host localhost --port 27017 --out H:\oplogOneDump
|
Where the oplogOneDump folder did not exist. A folder New Folder was created but not renamed to oplogOneDump folder at any point in the process, and the end result was in "New Folder"
The outpout continued to show that it was using H:\oplogOneDump but was actually using New Folder.
016-05-19T02:03:50.128+0000 writing dfl.eventsIntervalEntry to H:\oplogOneDump\dfl\eventsIntervalEntry.bson
|
016-05-19T02:03:50.131+0000 writing dfl.events to H:\oplogOneDump\dfl\events.bson
|
...
|
2016-05-19T06:30:44.418+0000 writing dfl.seriesEntry metadata to H:\oplogOneDump\dfl\seriesEntry.metadata.json
|
See attached image for view of final output in new folder.