verify should not panic

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • WT2.7.0
    • Affects Version/s: WT2.6.1
    • Component/s: None
    • None
    • Storage Engines
    • None
    • None

      From SERVER-19293.

      When verify is run on a database, it should not panic. An error should be returned instead because MongoDB will then run salvage, which will fix the problem.

      2015-07-06T13:49:53.972-0500 E STORAGE  [initandlisten] WiredTiger (0) [1436208593:972487][16105:0x7fe889ce5bc0], file:collection-1595-7140502635356682714.wt, session.verify: read checksum error [4096B @ 9994240, 832067279 != 2155579310]
2015-07-06T13:49:53.972-0500 E STORAGE  [initandlisten] WiredTiger (0) [1436208593:972512][16105:0x7fe889ce5bc0], file:collection-1595-7140502635356682714.wt, session.verify: collection-1595-7140502635356682714.wt: encountered an illegal file format or internal value
...
2015-07-06T13:49:53.972-0500 E STORAGE  [initandlisten] WiredTiger (-31804) [1436208593:972525][16105:0x7fe889ce5bc0], file:collection-1595-7140502635356682714.wt, session.verify: the process must exit and restart: WT_PANIC: WiredTiger library panic
...
 mongod(__wt_panic+0x24) [0x13914e4]
 mongod(__wt_block_extlist_read+0x6E) [0x12e228e]
 mongod(__wt_block_extlist_read_avail+0x28) [0x12e2728]
 mongod(+0xEE54CF) [0x12e54cf]
 mongod(__wt_block_verify_start+0x108) [0x12e5648]
 mongod(__wt_verify+0x4AA) [0x1310afa]

            Assignee:
            Michael Cahill (Inactive)
            Reporter:
            Michael Cahill (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: