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

Repair fails WT_CURSOR.next: read checksum error

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • None
    • 4.0.1
    • WiredTiger
    • ALL
    • Hide

      Maybe having a mongodb running on a NFS shared folder, kill it, and run two instance trying to repair.

      Show
      Maybe having a mongodb running on a NFS shared folder, kill it, and run two instance trying to repair.

    Description

      I have a micro-service cluster with a NFS share, normally only one instance of mongodb (docker's mongo) is running. After a crash of the cluster I cannot bring the DB back up, the repair fails violently:

      E STORAGE [initandlisten] WiredTiger error (0) [1547049030:493990][10:0x7f75f72aea00], file:WiredTiger.wt, WT_CURSOR.next: read checksum error for 28672B block at offset 16384: block header checksum of 806183382 doesn't match expected checksum of 619640434 Raw: [1547049030:493990][10:0x7f75f72aea00], file:WiredTiger.wt, WT_CURSOR.next: read checksum error for 28672B block at offset 16384: block header checksum of 806183382 doesn't match expected checksum of 619640434

       

      and displays multiple chunks of data.

      I'd appreciate any help in restoring the DB, it wasn't backed up and wasn't part of a replicate neither... I attached the faulty WiredTiger.wt, the mongod --repair output and the WiredTiger.turtle (as it seems to be useful for repairing).

      Attachments

        1. repair.log
          190 kB
        2. WiredTiger.turtle
          1 kB
        3. WiredTiger.wt
          128 kB

        Activity

          People

            kelsey.schubert@mongodb.com Kelsey Schubert
            foloex Rémi AUGUSTE
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: