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

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

    • Linux

      We run MongoDB 3.4.3 in an kubernetes cluster, the Mongo pod exsit and WiredTiger data files are corrupted. I copied data files to another volume and run Mongo repair command: mongod --repair, there’re errors like: WiredTiger error (-31802) [1514980856:210666][151:0x7fda0a758cc0], file:WiredTiger.wt, connection: unable to read root page from file:WiredTiger.wt: WT_ERROR: non-specific WiredTiger error

      Could you please have a look at this? Thank you!

      root@mongo2-rpg5s:/mnt/tmp# mongod --port 16000 --repair --dbpath /mnt/tmp/
      2018-01-03T12:00:56.191+0000 I CONTROL  [initandlisten] MongoDB starting : pid=151 port=16000 dbpath=/mnt/tmp/ 64-bit host=mongo2-rpg5s
      2018-01-03T12:00:56.191+0000 I CONTROL  [initandlisten] db version v3.4.3
      2018-01-03T12:00:56.191+0000 I CONTROL  [initandlisten] git version: f07437fb5a6cca07c10bafa78365456eb1d6d5e1
      2018-01-03T12:00:56.191+0000 I CONTROL  [initandlisten] OpenSSL version: OpenSSL 1.0.1t  3 May 2016
      2018-01-03T12:00:56.191+0000 I CONTROL  [initandlisten] allocator: tcmalloc
      2018-01-03T12:00:56.191+0000 I CONTROL  [initandlisten] modules: none
      2018-01-03T12:00:56.191+0000 I CONTROL  [initandlisten] build environment:
      2018-01-03T12:00:56.191+0000 I CONTROL  [initandlisten]     distmod: debian81
      2018-01-03T12:00:56.191+0000 I CONTROL  [initandlisten]     distarch: x86_64
      2018-01-03T12:00:56.191+0000 I CONTROL  [initandlisten]     target_arch: x86_64
      2018-01-03T12:00:56.191+0000 I CONTROL  [initandlisten] options: { net: { port: 16000 }, repair: true, storage: { dbPath: "/mnt/tmp/" } }
      2018-01-03T12:00:56.191+0000 W -        [initandlisten] Detected unclean shutdown - /mnt/tmp/mongod.lock is not empty.
      2018-01-03T12:00:56.196+0000 I -        [initandlisten] Detected data files in /mnt/tmp/ created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
      2018-01-03T12:00:56.196+0000 W STORAGE  [initandlisten] Recovering data from the last clean checkpoint.
      2018-01-03T12:00:56.196+0000 I STORAGE  [initandlisten] Detected WT journal files.  Running recovery from last checkpoint.
      2018-01-03T12:00:56.196+0000 I STORAGE  [initandlisten] journal to nojournal transition config: create,cache_size=7511M,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),
      2018-01-03T12:00:56.210+0000 E STORAGE  [initandlisten] WiredTiger error (-31802) [1514980856:210666][151:0x7fda0a758cc0], file:WiredTiger.wt, connection: unable to read root page from file:WiredTiger.wt: WT_ERROR: non-specific WiredTiger error
      2018-01-03T12:00:56.210+0000 E STORAGE  [initandlisten] WiredTiger error (0) [1514980856:210726][151:0x7fda0a758cc0], file:WiredTiger.wt, connection: WiredTiger has failed to open its metadata
      2018-01-03T12:00:56.210+0000 E STORAGE  [initandlisten] WiredTiger error (0) [1514980856:210737][151:0x7fda0a758cc0], file:WiredTiger.wt, connection: This may be due tothe database files being encrypted, being from an older version or due to corruption on disk
      2018-01-03T12:00:56.210+0000 E STORAGE  [initandlisten] WiredTiger error (0) [1514980856:210748][151:0x7fda0a758cc0], file:WiredTiger.wt, connection: You should confirmthat you have opened the database with the correct options including all encryption and compression options
      2018-01-03T12:00:56.211+0000 I -        [initandlisten] Assertion: 28718:-31802: WT_ERROR: non-specific WiredTiger error src/mongo/db/storage/wiredtiger/wiredtiger_kv_engine.cpp 251
      2018-01-03T12:00:56.211+0000 I STORAGE  [initandlisten] exception in initAndListen: 28718 -31802: WT_ERROR: non-specific WiredTiger error, terminating
      2018-01-03T12:00:56.211+0000 I NETWORK  [initandlisten] shutdown: going to close listening sockets...
      2018-01-03T12:00:56.211+0000 I NETWORK  [initandlisten] removing socket file: /tmp/mongodb-16000.sock
      2018-01-03T12:00:56.211+0000 I NETWORK  [initandlisten] shutdown: going to flush diaglog...
      2018-01-03T12:00:56.211+0000 I CONTROL  [initandlisten] now exiting
      2018-01-03T12:00:56.211+0000 I CONTROL  [initandlisten] shutting down with code:100
      
      

        1. repair_attempt.tar.gz
          3 kB
        2. sizeStorer.wt
          36 kB
        3. WiredTiger.turtle
          1.0 kB
        4. WiredTiger.wt
          60 kB

            Assignee:
            kelsey.schubert@mongodb.com Kelsey Schubert
            Reporter:
            KevinWong Kevin Wong [X]
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: