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

Fix an incorrect report of log corruption

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.6.9, 4.0.2, 4.1.2, WT3.2.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Engines 2018-07-30

      There was an evergreen failure after the recent merge of log corruption changes.

      [2018/07/25 19:05:23.875] Parent: Compatibility false in-mem log true
      [2018/07/25 19:05:23.875] Parent: Create 5 threads; sleep 10 seconds
      [2018/07/25 19:05:23.875] Kill child
      [2018/07/25 19:05:23.875] Open database, run recovery and verify content
      [2018/07/25 19:05:23.875] ./WiredTigerLog.0000000047: log record at position 3825664 has flag corruption 0x2d68
      [2018/07/25 19:05:23.875] ./WiredTigerLog.0000000047: log record at position 3825664 has unused[0] corruption 0x32
      [2018/07/25 19:05:23.875] ./WiredTigerLog.0000000047: log record at position 3825664 has unused[1] corruption 0x74
      [2018/07/25 19:05:23.875] ./WiredTigerLog.0000000047: log record at position 3825664 has memory len corruption 0x74322d68
      [2018/07/25 19:05:23.875] [1532558371:188067][4078:0x7fffa32b43c0], txn-recover: __log_salvageable_error, 2154: log file ./WiredTigerLog.0000000047 corrupted at position 3825664, use salvage to fix: WT_ERROR: non-specific WiredTiger error
      [2018/07/25 19:05:23.875] [1532558371:188089][4078:0x7fffa32b43c0], txn-recover: __wt_panic, 525: the process must exit and restart: WT_PANIC: WiredTiger library panic
      [2018/07/25 19:05:23.875] [1532558371:188094][4078:0x7fffa32b43c0], txn-recover: __wt_abort, 30: aborting WiredTiger library
      [2018/07/25 19:05:23.875] ./random_abort/smoke.sh: line 8:  4078 Abort trap: 6           $TEST_WRAPPER ./test_random_abort -m -t 10 -T 5
      

      Depending on the nature of the run, if log 47 is the last log record it could be a duplicate of WT-4112. The offset 3825664 is 0x3a6000 so this record is exactly on a 4k boundary.

            Assignee:
            donald.anderson@mongodb.com Donald Anderson
            Reporter:
            sue.loverso@mongodb.com Susan LoVerso
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: