[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 |
||
| Operating System: | Windows |
| Participants: |
| Description |
|
After rebooting the machine. Here the log data: 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: If i start the mongo server without the --journal argument the server starts correctly. |
| Comments |
| Comment by Patrick G. [ 21/Nov/11 ] |
|
unfortunately not. |
| 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. 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 |
| 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 ? |
| 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: No i didn't do any writes after starting. |
| 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? |