Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-7289

validate command should do more inexpensive tests

    • Type: Icon: Improvement Improvement
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 2.2.2, 2.3.0
    • Affects Version/s: 2.0.7, 2.2.0
    • Component/s: Storage
    • Labels:
      None
    • Fully Compatible

      The validate command does not do some cheap and easy tests for validation.

      1. The 'xprev' pointer in each extent in the extent list should point to the previous extent, or be null for the first extent
      2. The 'lastExtent' pointer in NamespaceDetails should point to the last extent
      3. If an exception is thrown while counting extents, the failing extent is not identified
      4. If an exception is thrown while counting extents, no count is reported
      5. If an exception is thrown while counting extents, the first extent is not validated and the check for 'xprev' in the first extent being null is skipped
      6. If an invalid signature is found in an extent, the value found is not reported and the extent is not identified
      7. The "self-pointer" 'myLoc' in an extent is not validated
      8. The extent size should be compared with Extent::minSize(), not zero

            Assignee:
            tad Tad Marshall
            Reporter:
            tad Tad Marshall
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: