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

WiredTiger.wt, connection: read checksum error for 4096B block at offset 36864

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Duplicate
    • Affects Version/s: 3.4.16
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Environment:
      Centos
    • Operating System:
      ALL

      Description

      I directly used tar to pack the whole directory of my running mongod instance, the mongo directory contains my dbpath with jounal enabled. But when I  copy my tar package to another volumn and want to restart the mongod instance, it fails. I know that there must be somet corruption happened since I didn't stop mongo writing when I tar the underlying data  files. Here I post the WiredTiger err log which append when I try to use WiredTiger command utils to salvage my dataset collection. It is almost the same err when I try "-repair"

      [1558933099:261604][16092:0x7fca5e8a7720], file:WiredTiger.wt, connection: read checksum error for 4096B block at offset 36864: block header checksum of 3775757528 doesn't match expected checksum of 1737734002
      [1558933099:261630][16092:0x7fca5e8a7720], file:WiredTiger.wt, connection: WiredTiger.wt: encountered an illegal file format or internal value
      [1558933099:261636][16092:0x7fca5e8a7720], file:WiredTiger.wt, connection: the process must exit and restart: WT_PANIC: WiredTiger library panic
      lt-wt: WT_PANIC: WiredTiger library panic
      
      

        Attachments

        1. sizeStorer.wt
          68 kB
        2. storage.bson
          0.1 kB
        3. WiredTiger
          0.0 kB
        4. WiredTiger.wt
          1.29 MB

          Issue Links

            Activity

              People

              Assignee:
              eric.sedor Eric Sedor
              Reporter:
              zhuangdanyang zhuangdanyang
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: