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

file:WiredTiger.wt read checksum error, mongodb won't start

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.2.1
    • Component/s: WiredTiger
    • ALL

      Hi all,
      I have to repair a mongodb-Setup. After a raid issue the server crashed. I tried to --repair but I got

      2016-07-26T09:04:23.280+0200 E STORAGE  [initandlisten] WiredTiger (0) [1469516663:280195][5673:0x7faad17ebc80], file:WiredTiger.wt, WT_CURSOR.search_near: read checksum error for 16384B block at offset 45056: calculated block checksum of 562858221 doesn't match expected checksum of 3119024118
      
      2016-07-26T09:04:23.280+0200 E STORAGE  [initandlisten] WiredTiger (0) [1469516663:280299][5673:0x7faad17ebc80], file:WiredTiger.wt, WT_CURSOR.search_near: WiredTiger.wt: encountered an illegal file format or internal value
      
      2016-07-26T09:04:23.280+0200 E STORAGE  [initandlisten] WiredTiger (-31804) [1469516663:280318][5673:0x7faad17ebc80], file:WiredTiger.wt, WT_CURSOR.search_near: the process must exit and restart: WT_PANIC: WiredTiger library panic
      

      So I tried to recover using the wt-Tools, (described here: http://www.alexbevi.com/blog/2016/02/10/recovering-a-wiredtiger-collection-from-a-corrupt-mongodb-installation/) but still, I got the same error. Every command used wit wt tools gives me the same.
      So now, I have no idea how to repair that file. Since everyone sends you files, I put the WiredTiger.wt into the Attachment box.

      Helps and hints are very much appreciated,
      regards,
      jm

        1. WiredTiger.wt
          60 kB
        2. WiredTiger.turtle
          0.9 kB
        3. repair-attempt.tar
          2 kB

            Assignee:
            kelsey.schubert@mongodb.com Kelsey Schubert
            Reporter:
            jm@mpex.de Joern Merkel
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: