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

Improve messages for checksum error

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • WT2.7.0
    • None
    • None

    Description

      Serviceability would be improved if the messages produced in case of checksum error were a little more verbose.

      Instead of

      2015-07-23T19:35:13.956+0200 E STORAGE  [conn725] WiredTiger (0) [1437672913:956359][64247:0x7ff6ff6aa700], file:factee_geographic/collection/19-4376327810822422286.wt, cursor.next: read checksum error [4096B @ 4692008960, 3560417636 != 0]
      

      Suggest for example (for the case where header checksum doesn't match pageref checksum):

      checkum error in file ...: checksum in header of block of length ... at offset ... is ..., expected ...
      

      or (for the case where computed checksum doesn't match checksum header):

      checkum error in file ...: checksum in header of block of length ... at offset ... is ... as expected, but checksum computed from content of block is ...
      

      Attachments

        Issue Links

          Activity

            People

              keith.bostic@mongodb.com Keith Bostic
              bruce.lucas@mongodb.com Bruce Lucas
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: