• Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Critical - P2 Critical - P2
    • None
    • Affects Version/s: 3.0.9
    • Component/s: WiredTiger
    • Labels:
      None
    • ALL
    • Hide

      Unexpected.

      Show
      Unexpected.

      My database got "WT_PANIC: WiredTiger library panic" with this error:

      2016-04-05T08:27:58.378-0500 E STORAGE [initandlisten] WiredTiger (-31802) [1459862878:378859][25768:0x7f7c72ec8bc0], file:collection-2-6214914092427755077.wt, session.checkpoint: file contains a corrupted WiredTigerCheckpoint.161919.alloc extent list, range 15758626944-15759745152 past end-of-file: WT_ERROR: non-specific WiredTiger error

      2016-04-05T08:27:58.378-0500 E STORAGE [initandlisten] WiredTiger (-31804) [1459862878:378915][25768:0x7f7c72ec8bc0], file:collection-2-6214914092427755077.wt, session.checkpoint: the process must exit and restart: WT_PANIC: WiredTiger library panic

      I tried to repair with --repair and the same thing happened.

      What I need to do to repair or discard corrupted data to get my database online? This server is a replica but my database is very large and it is costly to replicate from start.

      Log files includes:

      mongo.log.2016-04-05T07-46-39.bz2 - first error (log with several days)
      mongo.log.2016-04-05T09-46-49.bz2 - second error (clean initialization but without --reapair)
      mongo.log.2016-04-05T13-27-54 - subsequent startup with --repair.

      Obs.: You will see several time-consuming operations in the first log, but have been properly indexed. But I think this wasn't the problem here.

        1. mongo.log.2016-04-05T07-46-39.bz2
          106.84 MB
        2. mongo.log.2016-04-05T09-46-49.bz2
          2.56 MB
        3. mongo.log.2016-04-05T13-27-54
          7 kB

            Assignee:
            kelsey.schubert@mongodb.com Kelsey Schubert
            Reporter:
            lucasoares Lucas
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: