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

Corrupt WiredTiger.wt fails to recover

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.0.6, 3.0.10, 3.2.7
    • Component/s: WiredTiger
    • Labels:
    • Linux
    • Hide

      Don't know how to reproduce, here's how it happened to me:

      • run mongodb, add data & stop (April)
      • run system updates on ubuntu
      • try to start mongdb after 2 months.
      Show
      Don't know how to reproduce, here's how it happened to me: run mongodb, add data & stop (April) run system updates on ubuntu try to start mongdb after 2 months.

      Database with WT engine fails to recover.

      I've tried --repair but with no success.

      2016-06-15T01:44:12.459+0300 E STORAGE  [initandlisten] WiredTiger (0) [1465944252:459446][27643:0x7f3f5204cbc0], file:WiredTiger.wt, connection: read checksum error for 4096B block at offset 102400: block header checksum of 1099557987 doesn't match expected checksum of 106923698
      2016-06-15T01:44:12.459+0300 E STORAGE  [initandlisten] WiredTiger (0) [1465944252:459493][27643:0x7f3f5204cbc0], file:WiredTiger.wt, connection: WiredTiger.wt: encountered an illegal file format or internal value
      2016-06-15T01:44:12.459+0300 E STORAGE  [initandlisten] WiredTiger (-31804) [1465944252:459507][27643:0x7f3f5204cbc0], file:WiredTiger.wt, connection: the process must exit and restart: WT_PANIC: WiredTiger library panic
      2016-06-15T01:44:12.459+0300 I -        [initandlisten] Fatal Assertion 28558
      2016-06-15T01:44:12.469+0300 I CONTROL  [initandlisten] 
       0xfa8242 0xf454d9 0xf29706 0xdca081 0x13ff32c 0x13ff4dd 0x13ff954 0x134aa24 0x136697b 0x1364557 0x136544d 0x1390a5b 0x13fe6d9 0x13ca183 0x138dfc9 0xdb4153 0xdb1e70 0xab1dca 0x82f9b1 0x7fd249 0x7f3f5092dec5 0x82d6d7
      

      This is an older instance of mongodb on my computer, the mongodb version might be at fault.

      I've tried updating mongdb to the latest version (3.2.7), I get a different error but still no success

      2016-06-15T02:14:28.129+0300 E STORAGE  [initandlisten] WiredTiger (-31802) [1465946068:129595][29342:0x7fa307a4acc0], file:WiredTiger.wt, connection: unable to read root page from file:WiredTiger.wt: WT_ERROR: non-specific WiredTiger error
      2016-06-15T02:14:28.129+0300 E STORAGE  [initandlisten] WiredTiger (0) [1465946068:129657][29342:0x7fa307a4acc0], file:WiredTiger.wt, connection: WiredTiger has failed to open its metadata
      2016-06-15T02:14:28.129+0300 E STORAGE  [initandlisten] WiredTiger (0) [1465946068:129673][29342:0x7fa307a4acc0], file:WiredTiger.wt, connection: This may be due to the database files being encrypted, being from an older version or due to corruption on disk
      2016-06-15T02:14:28.129+0300 E STORAGE  [initandlisten] WiredTiger (0) [1465946068:129691][29342:0x7fa307a4acc0], file:WiredTiger.wt, connection: You should confirm that you have opened the database with the correct options including all encryption and compression options
      2016-06-15T02:14:28.130+0300 I -        [initandlisten] Assertion: 28718:-31802: WT_ERROR: non-specific WiredTiger error
      2016-06-15T02:14:28.130+0300 I STORAGE  [initandlisten] exception in initAndListen: 28718 -31802: WT_ERROR: non-specific WiredTiger error, terminating
      2016-06-15T02:14:28.130+0300 I CONTROL  [initandlisten] dbexit:  rc: 100
      

      Please help, no other backup available.

        1. _mdb_catalog.wt
          56 kB
        2. repair_attempt.tgz
          66 kB
        3. sizeStorer.wt
          128 kB
        4. storage.bson
          0.1 kB
        5. WiredTiger
          0.0 kB
        6. WiredTiger.basecfg
          0.5 kB
        7. WiredTiger.turtle
          0.9 kB
        8. WiredTiger.wt
          864 kB

            Assignee:
            ramon.fernandez@mongodb.com Ramon Fernandez Marina
            Reporter:
            stefan.rogin Stefan Rogin
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: