Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-18443

directoryPerDB option misleading error message when directory is already popluated

    XMLWordPrintable

    Details

    • Type: Question
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Duplicate
    • Affects Version/s: 3.0.2
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                mark.helmstetter Mark Helmstetter
                Participants:
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: