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

Missing or corrupt data files should cause MongoDB to exit with an error message to run repair

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.0.3, 4.1.2
    • Affects Version/s: None
    • Component/s: None
    • Fully Compatible
    • v4.0
    • Storage NYC 2018-07-16, Storage NYC 2018-07-30

      In any of the following cases during startup, MongoDB should exit with the same error message requiring the user to run --repair. The current behavior is a crash with no helpful information.

      • Missing or corrupt _mdb_catalog
      • Missing or corrupt WiredTiger.wt metadata
      • Missing or corrupt collections or indexes

            Assignee:
            xiangyu.yao@mongodb.com Xiangyu Yao (Inactive)
            Reporter:
            louis.williams@mongodb.com Louis Williams
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: