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

Corrupted files: calculated block checksum doesn't match expected checksum

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

      We've run into a massive issues with our database running on Windows Server 2019. For unknown reasons the data files has become corrupt and I'm having major isssues trying to restore them.

      What I've tried so far is to copy all the corrupt collection files one by one to a new mongodb instance and run the --repair command. Then I created a dump of the repaired collection, deleted the old corrupted collection on the original instance and restored it from the repaired dump.

      This did seem to solve the issues I had with the checksum error, but one of the collections got corrupted again, so it leads me to believe something is very wrong with the other files as well and not just the collections.

      Repairing the database was not a success and basically just killed the databse. Also tried to use the wiredtiger (wt) tool to salvage the data, but had no success in building the tool with snappy compression

      What would be the best approach?

      CheersĀ 

      Stefan

        1. WiredTiger.wt
          736 kB
        2. WiredTiger.turtle
          1 kB
        3. mongod.log
          163 kB

            Assignee:
            eric.sedor@mongodb.com Eric Sedor
            Reporter:
            stefanbohlin@gmail.com Stefan Bohlin
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: