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

WiredTiger.wt File corrupted , Server cannot start

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Done
    • 3.4.6
    • None
    • None
    • Windows

    Description

      After an unexpected shutdown, mongodb does not start properly. I have tried the --repair run with mongo:3.4.6, But not work.

      os : windows server

      start log is:

      2018-07-10T09:24:35.661+0800 I CONTROL  [initandlisten] options: { storage: { dbPath: "E:\servers\mongodb\data" } }
      2018-07-10T09:24:35.661+0800 W -        [initandlisten] Detected unclean shutdown - E:\servers\mongodb\data\mongod.lock is not empty.
      2018-07-10T09:24:35.662+0800 I -        [initandlisten] Detected data files in E:\servers\mongodb\data created by the 'wiredTiger' storage engine, so
      setting the active storage engine to 'wiredTiger'.
      2018-07-10T09:24:35.663+0800 W STORAGE  [initandlisten] Recovering data from the last clean checkpoint.
      2018-07-10T09:24:35.663+0800 I STORAGE  [initandlisten] wiredtiger_open config: create,cache_size=32199M,session_max=20000,eviction=(threads_min=4,thr
      eads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),c
      heckpoint=(wait=60,log_size=2GB),statistics_log=(wait=0),
      2018-07-10T09:24:35.672+0800 E STORAGE  [initandlisten] WiredTiger error (-31802) [1531185875:672589][4124:1991524064], file:WiredTiger.wt, connection
      : unable to read root page from file:WiredTiger.wt: WT_ERROR: non-specific WiredTiger error
      2018-07-10T09:24:35.673+0800 E STORAGE  [initandlisten] WiredTiger error (0) [1531185875:673589][4124:1991524064], file:WiredTiger.wt, connection: Wir
      edTiger has failed to open its metadata
      2018-07-10T09:24:35.673+0800 E STORAGE  [initandlisten] WiredTiger error (0) [1531185875:673589][4124:1991524064], file:WiredTiger.wt, connection: Thi
      s may be due to the database files being encrypted, being from an older version or due to corruption on disk
      2018-07-10T09:24:35.674+0800 E STORAGE  [initandlisten] WiredTiger error (0) [1531185875:674589][4124:1991524064], file:WiredTiger.wt, connection: You
       should confirm that you have opened the database with the correct options including all encryption and compression options
      2018-07-10T09:24:35.675+0800 I -        [initandlisten] Assertion: 28595:-31802: WT_ERROR: non-specific WiredTiger error src\mongo\db\storage\wiredtig
      er\wiredtiger_kv_engine.cpp 269
      2018-07-10T09:24:35.676+0800 I STORAGE  [initandlisten] exception in initAndListen: 28595 -31802: WT_ERROR: non-specific WiredTiger error, terminating2018-07-10T09:24:35.676+0800 I NETWORK  [initandlisten] shutdown: going to close listening sockets...
      2018-07-10T09:24:35.677+0800 I NETWORK  [initandlisten] shutdown: going to flush diaglog...
      2018-07-10T09:24:35.677+0800 I CONTROL  [initandlisten] now exiting
      2018-07-10T09:24:35.677+0800 I CONTROL  [initandlisten] shutting down with code:100
      

      Attachments

        1. _mdb_catalog.wt
          36 kB
        2. repair-attempt.tar.gz
          7 kB
        3. sizeStorer.wt
          60 kB
        4. WiredTiger
          0.0 kB
        5. WiredTiger.turtle
          1.0 kB
        6. WiredTiger.wt
          156 kB
        7. WiredTigerLAS.wt
          4 kB

        Activity

          People

            nick.brewer Nick Brewer
            lh83mail lh83mail
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: