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

Corrupt WiredTiger.wt file after crash

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

      We suffered a VM crash that housed a non replicated MongoDB server. I haven't been able to recover any of the data, using various steps found on JIRA (and StackOverflow). My best guess at this point is that the WiredTiger.wt got corrupted, so we can't start up the server.

      It seems VERY similar to this issue: https://jira.mongodb.org/browse/SERVER-31124?focusedCommentId=1675509&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-1675509

      I'm hoping you guys can help! I've attached the MongoDB folder & also the output of the startup attempt.

      2017-11-20T08:28:20.180+0200 I CONTROL  [initandlisten] MongoDB starting : pid=25121 port=27017 dbpath=/var/lib/mongodb/ 64-bit host=hc-dbn-vps01_old
      2017-11-20T08:28:20.180+0200 I CONTROL  [initandlisten] db version v3.2.16
      2017-11-20T08:28:20.181+0200 I CONTROL  [initandlisten] git version: 056bf45128114e44c5358c7a8776fb582363e094
      2017-11-20T08:28:20.181+0200 I CONTROL  [initandlisten] OpenSSL version: OpenSSL 1.0.2g  1 Mar 2016
      2017-11-20T08:28:20.181+0200 I CONTROL  [initandlisten] allocator: tcmalloc
      2017-11-20T08:28:20.181+0200 I CONTROL  [initandlisten] modules: none
      2017-11-20T08:28:20.181+0200 I CONTROL  [initandlisten] build environment:
      2017-11-20T08:28:20.181+0200 I CONTROL  [initandlisten]     distmod: ubuntu1604
      2017-11-20T08:28:20.181+0200 I CONTROL  [initandlisten]     distarch: x86_64
      2017-11-20T08:28:20.182+0200 I CONTROL  [initandlisten]     target_arch: x86_64
      2017-11-20T08:28:20.182+0200 I CONTROL  [initandlisten] options: { repair: true, storage: { dbPath: "/var/lib/mongodb/", engine: "wiredTiger" } }
      2017-11-20T08:28:20.220+0200 I STORAGE  [initandlisten] Detected WT journal files.  Running recovery from last checkpoint.
      2017-11-20T08:28:20.220+0200 I STORAGE  [initandlisten] journal to nojournal transition config: create,cache_size=1G,session_max=20000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),checkpoint=(wait=60,log_size=2GB),statistics_log=(wait=0),
      2017-11-20T08:28:20.230+0200 E STORAGE  [initandlisten] WiredTiger (-31802) [1511159300:229985][25121:0x7f7ce23f0c80], file:WiredTiger.wt, connection: unable to read root page from file:WiredTiger.wt: WT_ERROR: non-specific WiredTiger error
      2017-11-20T08:28:20.230+0200 E STORAGE  [initandlisten] WiredTiger (0) [1511159300:230288][25121:0x7f7ce23f0c80], file:WiredTiger.wt, connection: WiredTiger has failed to open its metadata
      2017-11-20T08:28:20.230+0200 E STORAGE  [initandlisten] WiredTiger (0) [1511159300:230475][25121:0x7f7ce23f0c80], 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
      2017-11-20T08:28:20.230+0200 E STORAGE  [initandlisten] WiredTiger (0) [1511159300:230657][25121:0x7f7ce23f0c80], file:WiredTiger.wt, connection: You should confirm that you have opened the database with the correct options including all encryption and compression options
      2017-11-20T08:28:20.231+0200 I -        [initandlisten] Assertion: 28718:-31802: WT_ERROR: non-specific WiredTiger error
      2017-11-20T08:28:20.231+0200 I STORAGE  [initandlisten] exception in initAndListen: 28718 -31802: WT_ERROR: non-specific WiredTiger error, terminating
      2017-11-20T08:28:20.232+0200 I CONTROL  [initandlisten] dbexit:  rc: 100
      

        1. repair-SERVER-32039.tar.gz
          6 kB
          Mark Agarunov

            Assignee:
            mark.agarunov Mark Agarunov
            Reporter:
            joduplessis Johannes du Plessis
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: