Put more debugging information when magic number does not match in the extents

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: 2.0.4
    • Component/s: Diagnostics
    • None
    • Storage Execution
    • ALL
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Whenever we get an assertion about this, we currently have little clue what is wrong other than it does not match. It would probably be more helpful if we dump the contents of the extent (length, myLoc, xnext, xprev, magic) as well as the next and previous extents.

            Assignee:
            [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: