[SERVER-13910] Not enought storage available Created: 12/May/14  Updated: 11/Jul/16  Resolved: 14/May/14

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

Type: Bug Priority: Major - P3
Reporter: Guillaume Androz [X] Assignee: Mark Benvenuto
Resolution: Done Votes: 0
Labels: Windows, crash
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows 7, 64bits, >100GB free space, virtual memory managed by the system


Operating System: Windows
Participants:

 Description   

Got this issue in my log files.
I'm unable to repair the database and I cant run MongoDB service anymore.

2014-05-12T15:11:03.711-0400 [FileAllocator] allocating new datafile C:\mongodb\data\db\dbTestJig.8, filling with zeroes...
2014-05-12T15:11:06.628-0400 [FileAllocator] done allocating datafile C:\mongodb\data\db\dbTestJig.8, size: 512MB, took 2.909 secs
2014-05-12T15:11:07.549-0400 [conn224] MapViewOfFileEx for C:\mongodb\data\db\dbTestJig.8 at address 00000000 failed with errno:8 Not enough storage is available to process this command. (file size is 536870912) in MemoryMappedFile::map
2014-05-12T15:11:07.985-0400 [conn224] dbTestJig.JigElements Fatal Assertion 16166
2014-05-12T15:11:38.640-0400 [conn224] mongod.exe ...\src\mongo\util\log.cpp(122) mongo::logContext+0xa7
2014-05-12T15:11:38.640-0400 [conn224] mongod.exe ...\src\mongo\util\assert_util.cpp(138) mongo::fassertFailed+0x92
2014-05-12T15:11:38.640-0400 [conn224] mongod.exe ...\src\mongo\util\mmap_win.cpp(211) mongo::MemoryMappedFile::map+0x6f9
2014-05-12T15:11:38.640-0400 [conn224] mongod.exe ...\src\mongo\db\storage\durable_mapped_file.cpp(151) mongo::DurableMappedFile::create+0xe5
2014-05-12T15:11:38.640-0400 [conn224] mongod.exe ...\src\mongo\db\storage\data_file.cpp(146) mongo::DataFile::open+0x14f
2014-05-12T15:11:38.640-0400 [conn224] mongod.exe ...\src\mongo\db\storage\extent_manager.cpp(161) mongo::ExtentManager::getFile+0x46a
2014-05-12T15:11:38.640-0400 [conn224] mongod.exe ...\src\mongo\db\storage\extent_manager.cpp(381) mongo::ExtentManager::createExtent+0xdc
2014-05-12T15:11:38.640-0400 [conn224] mongod.exe ...\src\mongo\db\storage\extent_manager.cpp(484) mongo::ExtentManager::increaseStorageSize+0x8b
2014-05-12T15:11:38.655-0400 [conn224] mongod.exe ...\src\mongo\db\structure\record_store.cpp(213) mongo::SimpleRecordStoreV1::allocRecord+0x12a
2014-05-12T15:11:38.655-0400 [conn224] mongod.exe ...\src\mongo\db\structure\record_store.cpp(95) mongo::RecordStoreV1Base::insertRecord+0x62
2014-05-12T15:11:38.655-0400 [conn224] mongod.exe ...\src\mongo\db\catalog\collection.cpp(233) mongo::Collection::_insertDocument+0x97
2014-05-12T15:11:38.655-0400 [conn224] mongod.exe ...\src\mongo\db\catalog\collection.cpp(190) mongo::Collection::insertDocument+0x1b4
2014-05-12T15:11:38.655-0400 [conn224] mongod.exe ...\src\mongo\db\commands\write_commands\batch_executor.cpp(1057) mongo::singleInsert+0x64
2014-05-12T15:11:38.655-0400 [conn224] mongod.exe ...\src\mongo\db\commands\write_commands\batch_executor.cpp(984) mongo::insertOne+0x14d
2014-05-12T15:11:38.655-0400 [conn224] mongod.exe ...\src\mongo\db\commands\write_commands\batch_executor.cpp(1019) mongo::WriteBatchExecutor::execOneInsert+0xa9
2014-05-12T15:11:38.655-0400 [conn224] mongod.exe ...\src\mongo\db\commands\write_commands\batch_executor.cpp(830) mongo::WriteBatchExecutor::execInserts+0x105
2014-05-12T15:11:38.655-0400 [conn224] mongod.exe ...\src\mongo\db\commands\write_commands\batch_executor.cpp(710) mongo::WriteBatchExecutor::bulkExecute+0x44
2014-05-12T15:11:38.655-0400 [conn224] mongod.exe ...\src\mongo\db\commands\write_commands\batch_executor.cpp(248) mongo::WriteBatchExecutor::executeBatch+0x4e7
2014-05-12T15:11:38.655-0400 [conn224] mongod.exe ...\src\mongo\db\commands\write_commands\write_commands.cpp(146) mongo::WriteCmd::run+0x1b8
2014-05-12T15:11:38.655-0400 [conn224] mongod.exe ...\src\mongo\db\dbcommands.cpp(1357) mongo::_execCommand+0x66
2014-05-12T15:11:38.655-0400 [conn224] dbTestJig.JigElements
2014-05-12T15:11:38.655-0400 [conn224]

***aborting after fassert() failure

2014-05-12T15:11:39.607-0400 [conn224] mongod.exe ...\src\mongo\util\signal_handlers.cpp(107) mongo::`anonymous namespace'::abruptQuit+0xd1
2014-05-12T15:11:39.607-0400 [conn224] mongod.exe f:\dd\vctools\crt_bld\self_x86\crt\src\winsig.c(586) raise+0x17a
2014-05-12T15:11:39.607-0400 [conn224] mongod.exe f:\dd\vctools\crt_bld\self_x86\crt\src\abort.c(74) abort+0x10
2014-05-12T15:11:39.607-0400 [conn224] mongod.exe ...\src\mongo\util\assert_util.cpp(142) mongo::fassertFailed+0xfd
2014-05-12T15:11:39.607-0400 [conn224] mongod.exe ...\src\mongo\util\mmap_win.cpp(211) mongo::MemoryMappedFile::map+0x6f9
2014-05-12T15:11:39.607-0400 [conn224] mongod.exe ...\src\mongo\db\storage\durable_mapped_file.cpp(151) mongo::DurableMappedFile::create+0xe5
2014-05-12T15:11:39.607-0400 [conn224] mongod.exe ...\src\mongo\db\storage\data_file.cpp(146) mongo::DataFile::open+0x14f
2014-05-12T15:11:39.607-0400 [conn224] mongod.exe ...\src\mongo\db\storage\extent_manager.cpp(161) mongo::ExtentManager::getFile+0x46a
2014-05-12T15:11:39.607-0400 [conn224] mongod.exe ...\src\mongo\db\storage\extent_manager.cpp(381) mongo::ExtentManager::createExtent+0xdc
2014-05-12T15:11:39.607-0400 [conn224] mongod.exe ...\src\mongo\db\storage\extent_manager.cpp(484) mongo::ExtentManager::increaseStorageSize+0x8b
2014-05-12T15:11:39.607-0400 [conn224] mongod.exe ...\src\mongo\db\structure\record_store.cpp(213) mongo::SimpleRecordStoreV1::allocRecord+0x12a
2014-05-12T15:11:39.607-0400 [conn224] mongod.exe ...\src\mongo\db\structure\record_store.cpp(95) mongo::RecordStoreV1Base::insertRecord+0x62
2014-05-12T15:11:39.607-0400 [conn224] mongod.exe ...\src\mongo\db\catalog\collection.cpp(233) mongo::Collection::_insertDocument+0x97
2014-05-12T15:11:39.607-0400 [conn224] mongod.exe ...\src\mongo\db\catalog\collection.cpp(190) mongo::Collection::insertDocument+0x1b4
2014-05-12T15:11:39.607-0400 [conn224] mongod.exe ...\src\mongo\db\commands\write_commands\batch_executor.cpp(1057) mongo::singleInsert+0x64
2014-05-12T15:11:39.607-0400 [conn224] mongod.exe ...\src\mongo\db\commands\write_commands\batch_executor.cpp(984) mongo::insertOne+0x14d
2014-05-12T15:11:39.607-0400 [conn224] mongod.exe ...\src\mongo\db\commands\write_commands\batch_executor.cpp(1019) mongo::WriteBatchExecutor::execOneInsert+0xa9
2014-05-12T15:11:39.607-0400 [conn224] mongod.exe ...\src\mongo\db\commands\write_commands\batch_executor.cpp(830) mongo::WriteBatchExecutor::execInserts+0x105
2014-05-12T15:11:39.607-0400 [conn224] mongod.exe ...\src\mongo\db\commands\write_commands\batch_executor.cpp(710) mongo::WriteBatchExecutor::bulkExecute+0x44
2014-05-12T15:11:39.607-0400 [conn224] mongod.exe ...\src\mongo\db\commands\write_commands\batch_executor.cpp(248) mongo::WriteBatchExecutor::executeBatch+0x4e7
2014-05-12T15:11:39.607-0400 [conn224] SEVERE: Got signal: 22 (SIGABRT).



 Comments   
Comment by Githook User [ 22/May/14 ]

Author:

{u'username': u'markbenvenuto', u'name': u'Mark Benvenuto', u'email': u'mark.benvenuto@mongodb.com'}

Message: SERVER-13910: Warn the user when running a 32-bit build on Win64

Windows 32 bit builds have less virtual memory available
then 64-bit builds, warn the user they should use a 64-bit build
over a 32-bit build.
Branch: master
https://github.com/mongodb/mongo/commit/473028b020ee8288a14eca1454d9c08e507ef001

Comment by Guillaume Androz [X] [ 14/May/14 ]

You were right. The MongoDB edition was the 32 bits one, it was not upgraded to 64 bits with the system.. I juste change it, delete the .lock file in the data and everything is fine now.
Thanks a lot !

Comment by Mark Benvenuto [ 14/May/14 ]

Download http://download.sysinternals.com/files/Sigcheck.zip, and run sigcheck.exe on your mongod.exe to check if it is 32 or 64. If it reports 32-bit like my example below, download the matching 64-bit version. If you are unsure what version of mongod.exe you have, just run mongod.exe --version.

sigcheck.exe mongod.exe

Output

mongod.exe:
        ...
        MachineType:    32-bit

Comment by Guillaume Androz [X] [ 14/May/14 ]

Actually, I am unable to restart server, neither windows service. It is possible that the Mongo edition is the 32bits as it was running on a former 32 bits sytem upgraded to a 64 bits one, but I dont know if the mongo edition was also improved. I'll check that and give news. But for now, how could I restart server ? I tried to delete the .lock file, then run command mongod --repair, but it is refused the same way that when I try to run mongod --config <config file>

Comment by Mark Benvenuto [ 13/May/14 ]

I suspect that you are running MongoDB 32-bit edition which limits all dbs to a total size of 2 GB due to the limits of 32-bit memory addressing. You can fix this using the 64-bit version of MongoDB to fix.

Run the following commands on your machine to help me understand your issue.

In mongo.exe, run to help identify your build, and send me the output.

db.runCommand("buildinfo")

In Windows cmd.exe, run

set PROCESSOR

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