Recovery does not run after database opened with recover=error

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 3.4.11, 3.6.0-rc2, WT3.0.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage 2017-10-23
    • None
    • v3.4

      In the new test I wrote for WT-3257, I discovered a bug that if I run with log=(recover=error) on an unclean directory (properly getting the error that recovery must be run) and then, on the same unclean database, I run log=(recover=on) it does not properly recover all the data. The error run the first time moves a checkpoint LSN forward and we skip the earlier data.

              Assignee:
              Susan LoVerso (Inactive)
              Reporter:
              Susan LoVerso (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: