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

Removed WiredTiger.turtle then all databases are gone

    • Type: Icon: Question Question
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.2.12
    • Component/s: None
    • Environment:
      Cent OS

      I'm a mongodb beginner from Shenzhen, China, today morning , I ran into a big trouble with mongoDB

      I removed the files below for `service mongod start', then everything goes wrong
      rm mongod.lock
      rm WiredTiger.turtle
      It's really a mitaken I've ever made, then I googled it and tried to repair by command ` mongod --repair`,
      it seems work, but when I try to `show dbs` via the mono shell, there is no db exits any more,
      all my databases have gone...
      afterwards, I google the error log many time , and I have to write to you for help, attaching some files if you need.
      Please reply to me as you will , I really need your help and thank you very much. Please?

      kind regards,

      Tang

        1. error.output.log
          8 kB
          zhixin tang
        2. mongod.conf
          0.8 kB
          zhixin tang
        3. mongod.log
          30 kB
          zhixin tang
        4. WiredTiger.lock
          0.0 kB
          zhixin tang
        5. WiredTiger.turtle
          1.0 kB
          zhixin tang
        6. WiredTiger.turtle.bak
          1.0 kB
          zhixin tang
        7. WiredTiger.turtle.bak2
          1.0 kB
          zhixin tang
        8. WiredTiger.wt.2
          124 kB
          zhixin tang
        9. WiredTiger.wt.3
          10.15 MB
          zhixin tang
        10. WiredTiger.wt.9
          44 kB
          zhixin tang
        11. WiredTiger.wt2
          32 kB
          zhixin tang

            Assignee:
            kelsey.schubert@mongodb.com Kelsey Schubert
            Reporter:
            ninetang zhixin tang
            Votes:
            0 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: