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

Log recovery should not ignore corruption in the middle of the last log file

    • Type: Icon: Improvement Improvement
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: WT3.0.0
    • Component/s: None
    • Labels:
      None

      This is related to the work in WT-3276.  If corruption is inserted in the middle of the final (most recent) log file, in the pre-zeroed portion of that file, the corruption is ignored, recovery completes and all records are visible. This is the current behavior without any changes for WT-3276. Recovery should in fact fail, and salvage should truncate the log at the point of corruption.

      The work for WT-3276 contains a new test_txn19.py that has an NOTE: comment to highlight the trouble area.
       

            Assignee:
            donald.anderson@mongodb.com Donald Anderson
            Reporter:
            donald.anderson@mongodb.com Donald Anderson
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: