Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-4345

Set corruption and return salvage on facing a missing log file

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical - P2
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.0.5, 4.1.6, WT3.2.0
    • Component/s: None
    • Labels:
      None
    • Story Points:
      5
    • Sprint:
      Storage Engines 2018-11-19
    • Backport Requested:
      v4.0

      Description

      In WT-4149 the ability to run salvage recovery in the face of a missing (middle) log file in recovery was added. Calling wiredtiger_open and running recovery will detect the missing log file. Calling wiredtiger_open(salvage=true) will recover what it can up to the point of the missing file.

      The problem is that the first call to wiredtiger_open that detects the issue does not return WT_TRY_SALVAGE. Instead it returns WT_PANIC.

      The logging code does not set WT_CONN_DATA_CORRUPTION. And wt_txn_recover returns ENOENT from the recovery attempt.

      The unit test, test_txn19.py is passing because it is looking for the first run to show No such file in the error output. It should verify that WT_TRY_SALVAGE is returned.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              sulabh.mahajan Sulabh Mahajan
              Reporter:
              sue.loverso Susan LoVerso
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: