[SERVER-4318] Assertion: 13636:file /data/db/production.5 open/create failed in createPrivateMap (look in log for more information) Created: 18/Nov/11  Updated: 29/May/12  Resolved: 21/Nov/11

Status: Closed
Project: Core Server
Component/s: Stability
Affects Version/s: 2.0.0
Fix Version/s: None

Type: Bug Priority: Critical - P2
Reporter: Patrick G. Assignee: Unassigned
Resolution: Incomplete Votes: 0
Labels: Windows, crash
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows 7 32 Bit
4.0 GB RAM


Operating System: Windows
Participants:

 Description   

After rebooting the machine.
The mongo Server fails while starting with --journal argument.

Here the log data:
createPrivateMap failed /data/db/production.5 errno:8 Für diesen Befehl ist nicht genügend Speicher verfügbar. filelen:536608768 (32 bit build)
Fri Nov 18 15:32:48 [conn2] Assertion: 13636:file /data/db/production.5 open/create failed in createPrivateMap (look in log for more information)
Fri Nov 18 15:32:48 [conn2] command admin.$cmd command:

{ listDatabases: 1 }

ntoreturn:1 exception: file /data/db/production.5 open/create failed in createPrivateMap (look in log for more information) code:13636 reslen:205 142ms

The translation for:
Für diesen Befehl ist nicht genügend Speicher verfügbar.
should be:
Not enough storage is available to process this command

If i start the mongo server without the --journal argument the server starts correctly.
But unfortunately with lost data in a collection.



 Comments   
Comment by Patrick G. [ 21/Nov/11 ]

unfortunately not.
Cause i didn't append to a file.

Comment by Eliot Horowitz (Inactive) [ 21/Nov/11 ]

If you have the logs would be great if you could send just so we could take a look

Comment by Patrick G. [ 20/Nov/11 ]

Nothing that i know.
But my data is back after dumping and restoring.
So everything went fine.

Thanks for your help.

Comment by Eliot Horowitz (Inactive) [ 19/Nov/11 ]

When you brought it back up without journal, what did you do while it was up?

Comment by Patrick G. [ 19/Nov/11 ]

Now i upgraded to a 64-bit Host and mongo runs now again with the --journal argument.

Unfortunatetly i lost a lot of data in one collection.

Curiously enough the data file is about 100MB but in the collection self i see just the "_id" field
nothing else.

Comment by Eliot Horowitz (Inactive) [ 18/Nov/11 ]

Yes - that's a size in bytes of a file mongo wants to allocate.

Comment by Patrick G. [ 18/Nov/11 ]

Is this "536608768" the value mongo tries to allocate memory ?
Which unit is this ?

Comment by Eliot Horowitz (Inactive) [ 18/Nov/11 ]

Hard to say why the system needs more space - but the error is from running out of virtual space.

Journalling needs more virtual space than without - which is why it starts without --journal

Comment by Patrick G. [ 18/Nov/11 ]

I didn't understand:
Why should i upgrade to a 64bit Host ?
Everything wen't fine until the restart.

No i didn't do any writes after starting.
I just started the mongo shell

Comment by Eliot Horowitz (Inactive) [ 18/Nov/11 ]

You need to upgrade to a 64-bit host.

If you started without --journal - you need to shutdown immediately.

Did you do any writes after starting?

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