[SERVER-6501] MongoDB on Windows failing because of lack of storage Created: 18/Jul/12  Updated: 15/Aug/12  Resolved: 18/Jul/12

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: 2.1.2
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Zhehao Mao Assignee: Andy Schwerin
Resolution: Done Votes: 0
Labels: crash, storage, windows
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows Server 2008 on Amazon EC2 small instance


Attachments: File mongo.dmp     Text File server.log    
Operating System: Windows
Participants:

 Description   

I'm trying to get the performance benchmarks running on Windows and I'm running into a weird bug. I ran the docgen tool to set up 5 databases of 250MB each. But partway through the server crashes. I checked the logs and saw this message.

MapViewOfFileEx for D:/datadb/small1.5 failed with errno:8 Not enough storage is available to process this command. (file size is 536608768) in MemoryMappedFile::map

I checked the storage size and there is plenty of free space (29.2 GB free on 32 GB volume). So I'm not sure what's going on. I've attached the server log and a core dump.



 Comments   
Comment by Andy Schwerin [ 18/Jul/12 ]

This is a 32-bit mongod. See the top several lines of the attached log. You're limited to 2 GB of virtual address space on 32-bit Windows, which means <<2GB of database data.

Comment by Eric Milkie [ 18/Jul/12 ]

By "storage", the error message is referring to virtual address space, not free disk space. How big is your paging file?
You can run vmmap.exe and point it at mongod while you're running the test, and that should show exactly why you're running out of memory.

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