directoryPerDB option misleading error message when directory is already popluated

XMLWordPrintableJSON

    • Type: Question
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: 3.0.2
    • Component/s: None
    • None
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      If I try to start mongod with a dbpath that is already populated, I get the following error message:

      2015-05-12T16:25:54.044-0400 I STORAGE [initandlisten] exception in initAndListen: 72 Metadata contains unexpected value storage engine option for directoryPerDBExpected true but got falseinstead, terminating

      This applies to both the default and wiredTiger storage engines.

              Assignee:
              Unassigned
              Reporter:
              Mark Helmstetter
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: