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

WiredTiger error (0) [1504527896:382615][91756:0x7f6ef4ecfd40], file:WiredTiger.wt, connection: read checksum error for 4096B block at offset 53248: block header checksum of 3729987182 doesn't match expected checksum of 2115544974

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Done
    • 3.4.3
    • None
    • WiredTiger
    • ALL
    • Hide

      2017-09-04T20:24:56.326+0800 I CONTROL [initandlisten] options: { repair: true, storage:

      { dbPath: "/share/MongoData/", engine: "wiredTiger" }

      }
      2017-09-04T20:24:56.364+0800 I STORAGE [initandlisten] Detected WT journal files. Running recovery from last checkpoint.
      2017-09-04T20:24:56.364+0800 I STORAGE [initandlisten] journal to nojournal transition config: create,cache_size=7406M,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-09-04T20:24:56.382+0800 E STORAGE [initandlisten] WiredTiger error (0) [1504527896:382615][91756:0x7f6ef4ecfd40], file:WiredTiger.wt, connection: read checksum error for 4096B block at offset 53248: block header checksum of 3729987182 doesn't match expected checksum of 2115544974
      2017-09-04T20:24:56.382+0800 E STORAGE [initandlisten] WiredTiger error (0) [1504527896:382670][91756:0x7f6ef4ecfd40], file:WiredTiger.wt, connection: WiredTiger.wt: encountered an illegal file format or internal value
      2017-09-04T20:24:56.382+0800 E STORAGE [initandlisten] WiredTiger error (-31804) [1504527896:382688][91756:0x7f6ef4ecfd40], file:WiredTiger.wt, connection: the process must exit and restart: WT_PANIC: WiredTiger library panic
      2017-09-04T20:24:56.382+0800 I - [initandlisten] Fatal Assertion 28558 at src/mongo/db/storage/wiredtiger/wiredtiger_util.cpp 361
      2017-09-04T20:24:56.382+0800 I - [initandlisten]

      ***aborting after fassert() failure

      Show
      2017-09-04T20:24:56.326+0800 I CONTROL [initandlisten] options: { repair: true, storage: { dbPath: "/share/MongoData/", engine: "wiredTiger" } } 2017-09-04T20:24:56.364+0800 I STORAGE [initandlisten] Detected WT journal files. Running recovery from last checkpoint. 2017-09-04T20:24:56.364+0800 I STORAGE [initandlisten] journal to nojournal transition config: create,cache_size=7406M,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-09-04T20:24:56.382+0800 E STORAGE [initandlisten] WiredTiger error (0) [1504527896:382615] [91756:0x7f6ef4ecfd40] , file:WiredTiger.wt , connection: read checksum error for 4096B block at offset 53248: block header checksum of 3729987182 doesn't match expected checksum of 2115544974 2017-09-04T20:24:56.382+0800 E STORAGE [initandlisten] WiredTiger error (0) [1504527896:382670] [91756:0x7f6ef4ecfd40] , file:WiredTiger.wt , connection: WiredTiger.wt: encountered an illegal file format or internal value 2017-09-04T20:24:56.382+0800 E STORAGE [initandlisten] WiredTiger error (-31804) [1504527896:382688] [91756:0x7f6ef4ecfd40] , file:WiredTiger.wt , connection: the process must exit and restart: WT_PANIC: WiredTiger library panic 2017-09-04T20:24:56.382+0800 I - [initandlisten] Fatal Assertion 28558 at src/mongo/db/storage/wiredtiger/wiredtiger_util.cpp 361 2017-09-04T20:24:56.382+0800 I - [initandlisten] ***aborting after fassert() failure

    Description

      My sever lost power when I was backuping mongodb files,then I can't start mongo services,and I use the --repair order to repair it, this error message show.my mongodb version is v3.4.3 64bit, and I tried to replace the 'WiredTiger.turtle' and ‘WiredTiger.wt’ which you give in other similar issue like https://jira.mongodb.org/browse/SERVER-18448, it didn't work.Can you help me fix this problem?

      Attachments

        Activity

          People

            kelsey.schubert@mongodb.com Kelsey T Schubert
            libo yanglibo
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: