[SERVER-6068] MongoDump fails with a strange error Created: 11/Jun/12  Updated: 15/Aug/12  Resolved: 05/Jul/12

Status: Closed
Project: Core Server
Component/s: Tools
Affects Version/s: 2.0.2
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Eugene Shustef Assignee: Eric Milkie
Resolution: Incomplete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows 2008 Server running on AWS. Mongo files are on a persistent EBS drive.


Attachments: GIF File Capture.GIF    
Operating System: Windows
Participants:

 Description   

During execution of mongodump, the process fails with a strange error. The screencapture is attached.



 Comments   
Comment by Eugene Shustef [ 03/Jul/12 ]

Yup, all set

Comment by Eric Milkie [ 01/Jul/12 ]

Hi Eugene, did the mongodump successfully complete eventually?

Comment by Eric Milkie [ 11/Jun/12 ]

You can run db.stats() in the shell to see the size of the database you're dumping – how big is it? It looks like in your screen shot, it only through 16 million of the 53 million objects before it hit the error.

Comment by Eugene Shustef [ 11/Jun/12 ]

Yes, it's a full path - d:\backup. Mongodump then creates d:\backup[dbname] folder. There is about 160GBs left on that drive. The task is running now and hasn't blown up so far.

Comment by Eric Milkie [ 11/Jun/12 ]

Are you giving the full path? What is backup_folder? How much freespace is remaining on drive?

Comment by Eugene Shustef [ 11/Jun/12 ]

mongodump --db [dbname] --out [drive]:[backup_folder]

Comment by Eric Milkie [ 11/Jun/12 ]

Not sure. The mongodump source code returning the error is rather simple, just an fwrite() to the output file. fwrite() here is returning 0 and errno is getting set to 28 (no space left on device).
What's the commandline you are using?

Comment by Eugene Shustef [ 11/Jun/12 ]

There is plenty of space left on the disk where the backup goes. Could it be that it tried to write to a temp file in RAM and doesn't get enough RAM to write to?

Comment by Eric Milkie [ 11/Jun/12 ]

errno 28 is typically "no space left on device". Windows must have the "no paper left in printer" text for that error instead.

Generated at Thu Feb 08 03:10:40 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.