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

Unable to recover after fassert(): too many open files

XMLWordPrintableJSON

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

      1) Write to database, get 'too many files' exception
      2) Restart daemon (see everything has gone)
      3) Try to recover to new directory (/data/db1)
      4) Restart daemon (everything still gone)
      5) Restart machine
      6) Be unable to restart daemon

      Show
      1) Write to database, get 'too many files' exception 2) Restart daemon (see everything has gone) 3) Try to recover to new directory (/data/db1) 4) Restart daemon (everything still gone) 5) Restart machine 6) Be unable to restart daemon
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Hey guys,

      My databases and all collections just disappeared after a crash.
      It looks something like https://jira.mongodb.org/browse/SERVER-19774.
      It started off with the crash (could restart daemon but without databases and collections) and now I can no longer start the daemon. (I have about a week to finish running experiments for my thesis so any help on recover is much appreciated).

      I've described the issue here: http://stackoverflow.com/questions/38004375/mongodb-databases-disappeared?noredirect=1#comment63461612_38004375

      Please let me know whatever you need and I'll make sure you get it.

      It should be noted last I checked one database was 5GB and the other was < 500 MB.

        1. collect.py
          8 kB
          zeerak waseem
        2. linguistic_feats.py
          4 kB
          zeerak waseem
        3. mongo.log
          3.67 MB
          zeerak waseem

            Assignee:
            Unassigned Unassigned
            Reporter:
            zeerakw zeerak waseem
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: