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

file:WiredTiger.wt, connection: unable to read root page from file:WiredTiger.wt: WT_ERROR: non-specific WiredTiger error

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

      We run MongoDB 3.4.9 on Windows Server. Since some disk problems,  WiredTiger data files are corrupted. I copied data files to another server and tried to repair them using mongod --repair, then i got errors below.

      Now i need some help to repair the files. Thank you!

       

      2019-05-06T15:05:52.151+0800 I CONTROL [initandlisten] MongoDB starting : pid=20012 port=27017 dbpath=/data/db 64-bit host=DockerRegistry
      2019-05-06T15:05:52.152+0800 I CONTROL [initandlisten] db version v3.4.9
      2019-05-06T15:05:52.152+0800 I CONTROL [initandlisten] git version: 876ebee8c7dd0e2d992f36a848ff4dc50ee6603e
      2019-05-06T15:05:52.152+0800 I CONTROL [initandlisten] OpenSSL version: OpenSSL 1.0.2g 1 Mar 2016
      2019-05-06T15:05:52.152+0800 I CONTROL [initandlisten] allocator: tcmalloc
      2019-05-06T15:05:52.152+0800 I CONTROL [initandlisten] modules: none
      2019-05-06T15:05:52.152+0800 I CONTROL [initandlisten] build environment:
      2019-05-06T15:05:52.152+0800 I CONTROL [initandlisten] distmod: ubuntu1604
      2019-05-06T15:05:52.152+0800 I CONTROL [initandlisten] distarch: x86_64
      2019-05-06T15:05:52.152+0800 I CONTROL [initandlisten] target_arch: x86_64
      2019-05-06T15:05:52.152+0800 I CONTROL [initandlisten] options: { repair: true, storage:

      { dbPath: "/data/db" }

      }
      2019-05-06T15:05:52.152+0800 W - [initandlisten] Detected unclean shutdown - /data/db/mongod.lock is not empty.
      2019-05-06T15:05:52.200+0800 I - [initandlisten] Detected data files in /data/db created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
      2019-05-06T15:05:52.200+0800 W STORAGE [initandlisten] Recovering data from the last clean checkpoint.
      2019-05-06T15:05:52.200+0800 I STORAGE [initandlisten]
      2019-05-06T15:05:52.200+0800 I STORAGE [initandlisten] ** WARNING: Using the XFS filesystem is strongly recommended with the WiredTiger storage engine
      2019-05-06T15:05:52.200+0800 I STORAGE [initandlisten] ** See http://dochub.mongodb.org/core/prodnotes-filesystem
      2019-05-06T15:05:52.200+0800 I STORAGE [initandlisten] Detected WT journal files. Running recovery from last checkpoint.
      2019-05-06T15:05:52.200+0800 I STORAGE [initandlisten] journal to nojournal transition config: create,cache_size=3478M,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),
      2019-05-06T15:05:52.223+0800 E STORAGE [initandlisten] WiredTiger error (-31802) [1557126352:223732][20012:0x7f2c7ea681c0], file:WiredTiger.wt, connection: unable to read root page from file:WiredTiger.wt: WT_ERROR: non-specific WiredTiger error
      2019-05-06T15:05:52.223+0800 E STORAGE [initandlisten] WiredTiger error (0) [1557126352:223805][20012:0x7f2c7ea681c0], file:WiredTiger.wt, connection: WiredTiger has failed to open its metadata
      2019-05-06T15:05:52.223+0800 E STORAGE [initandlisten] WiredTiger error (0) [1557126352:223817][20012:0x7f2c7ea681c0], 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
      2019-05-06T15:05:52.223+0800 E STORAGE [initandlisten] WiredTiger error (0) [1557126352:223827][20012:0x7f2c7ea681c0], file:WiredTiger.wt, connection: You should confirm that you have opened the database with the correct options including all encryption and compression options
      2019-05-06T15:05:52.224+0800 I - [initandlisten] Assertion: 28718:-31802: WT_ERROR: non-specific WiredTiger error src/mongo/db/storage/wiredtiger/wiredtiger_kv_engine.cpp 253
      2019-05-06T15:05:52.224+0800 I STORAGE [initandlisten] exception in initAndListen: 28718 -31802: WT_ERROR: non-specific WiredTiger error, terminating
      2019-05-06T15:05:52.224+0800 I NETWORK [initandlisten] shutdown: going to close listening sockets...
      2019-05-06T15:05:52.224+0800 I NETWORK [initandlisten] removing socket file: /tmp/mongodb-27017.sock
      2019-05-06T15:05:52.224+0800 I NETWORK [initandlisten] shutdown: going to flush diaglog...
      2019-05-06T15:05:52.224+0800 I CONTROL [initandlisten] now exiting
      2019-05-06T15:05:52.224+0800 I CONTROL [initandlisten] shutting down with code:100

        1. repair.tar
          300 kB
        2. WiredTiger.turtle
          1.0 kB
        3. WiredTiger.wt
          292 kB

            Assignee:
            daniel.hatcher@mongodb.com Danny Hatcher (Inactive)
            Reporter:
            cywlarry Larry
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: