[SERVER-1329] "can't map file memory" after map/reduce gets interrupted Created: 30/Jun/10  Updated: 30/Mar/12  Resolved: 29/Sep/10

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

Type: Bug Priority: Major - P3
Reporter: Moe Loepi Assignee: Eliot Horowitz (Inactive)
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Ubuntu 10.04 LTS 64 Bit


Operating System: Linux
Participants:

 Description   

I started the mongod server at the console with -vvv verbose level. On another console I then tried to run a complex map/reduce query. As it took quite a while I killed the query with ctrl-c. As the map/reduce function still seemed to be running on the server I also shut down the server process by pressing ctrl-c.

After that I was unable to access any data in the database. Allthough I could switch to the database, every other command resulted in following error message:

can't map file memory

Also if I tried to run db.repairDatabase() I'll got this error message

{
"assertion" : "can't map file memory",
"errmsg" : "db assertion failure",
"ok" : 0
}

The only thing that helped to bring the database back was to run mongod --repair

Of course I'm aware that pressing ctrl-c is not the correct way of shutting down a server. However, it shouldn't result in such a severe breakdown of service if a not yet finished command gets interrupted.



 Comments   
Comment by Eliot Horowitz (Inactive) [ 05/Jul/10 ]

Trying to reproduce would be great.
especialyl on 1.5.4 if you can on a dev server.

Comment by Moe Loepi [ 05/Jul/10 ]

Unfortunately the server log isn't available as this occured on a temporary development server.

But I can try to reproduce it and to attach the log then.

Comment by Eliot Horowitz (Inactive) [ 30/Jun/10 ]

Can you attach the server log?

Depending on what it was doing - until there is single server durability (1.8) the --repair is definitely the correct solution.

Generated at Thu Feb 08 02:56:43 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.