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

Make log corruption checking work regardless of the machine byte order

XMLWordPrintableJSON

    • 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

      See http://build.wiredtiger.com:8080/job/wiredtiger-test-format-stress-zseries/43939/consoleFull ,

      get the following error:

      ./WiredTigerLog.0000000001: log record at position 224552576 has flag corruption 200
      [1532466578:560544][3739:0x3ff8aa74710], t, txn-recover: __log_salvageable_error, 2144: log file ./WiredTigerLog.0000000001 corrupted at position 224552576, use salvage to fix: WT_ERROR: non-specific WiredTiger error
      [1532466578:560560][3739:0x3ff8aa74710], t, txn-recover: __wt_panic, 525: the process must exit and restart: WT_PANIC: WiredTiger library panic
      [1532466578:560577][3739:0x3ff8aa74710], t, txn-recover: __wt_abort, 30: aborting WiredTiger library
      t: process 40370

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

              Created:
              Updated:
              Resolved: