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

Always return WT_TRY_SALVAGE for corrupted log

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: WT3.2.2, 4.3.3
    • Component/s: None
    • Labels:
    • Story Points:
      3
    • Sprint:
      Storage Engines 2019-12-02, Storage Engines 2019-12-16

      Description

      As a followup to WT-4344, there are some cases for which a damaged/missing/truncated log file will give an error other than WT_TRY_SALVAGE.  The easiest way to see this is to edit test_txn19.py and in this fragment:

               if expect_fail:
                   self.check_file_contains_one_of(errfile,
                       ['/log file.*corrupted/',
                       'WT_TRY_SALVAGE: database corruption detected'])
      

      remove the log file.*corrupted line.  This produces failures for cases where are log file is either zero length or begins with garbage.  For those cases we don't get WT_TRY_SALVAGE, but do get a log file...corrupted message. Presumably having an accurate return value will allow MongoDB to suggest the best course of action for recovery.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                haseeb.bokhari Haseeb Bokhari
                Reporter:
                donald.anderson Donald Anderson
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: