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

Always return WT_TRY_SALVAGE for corrupted log

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • WT10.0.0, 4.3.3, 4.2.3
    • Affects Version/s: None
    • Component/s: None
    • 3
    • Storage Engines 2019-12-02, Storage Engines 2019-12-16

      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.

            Assignee:
            haseeb.bokhari@mongodb.com Haseeb Bokhari (Inactive)
            Reporter:
            donald.anderson@mongodb.com Donald Anderson
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: