Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am having some troubles with MongoDB and space usage. In particular, I once used to have a large collection of about 600 million records totaling 110+ GB on disk. Recently I decided to drop it because the data was outdated, to do so I dropped the collection through rockmongo's web interface. Accordingly, rockmongo doesn't show me the collection anymore, however my disk usage hasn't changed at all.

Is there any clean operation which I am not aware of, which must be run in order to synchronize the database with database files on disk?

I have tried to perform a "repair" but the system complains that there's not enough space on disk ... that's because it is all used by MongoDB.

share|improve this question

migrated from May 15 '11 at 7:16

This question came from our site for professional and enthusiast programmers.

up vote 12 down vote accepted

As with most database systems, the database files does not shrink when you delete data, the data is just removed/marked as deleted, and the space is reused.

You'll need to run db.repairDatabase() to compact space as noted here

share|improve this answer
Hard disk space was too low to do that. However I solved this way: mongodump, oldDatabase.dropDatabase(), mongorestore --db newDatabase dump/oldDatabase. – tunnuz May 12 '11 at 13:43

While the above mongodump/drop/mongorestore approach will work fine from a technical perspective, it will require you to take the database offline while you do so, which would be a service-affecting event.

If you would like do this without downtime AND if you are using MongoDB Replica Sets[1], you could do so like this:

  1. Select a member and stop the MongoDB there (service mongodb stop). If this was the PRIMARY, wait for another member to be elected the PRIMARY.
  2. Remove the data files on this member (cd /var/lib/mongodb; rm *).
  3. Restart MongoDB service again (service mongodb start).
  4. Wait for the member to resync to the PRIMARY (rs.status()).
  5. This will rebuild only the required (smaller) data files.

Then repeat the above steps for each of the other members in the Replica Set.


share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.